Closed Bug 10336 Opened 20 years ago Closed 20 years ago

[BLOCKER] Please move entities into DTDs

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3, blocker)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tao, Assigned: alecf)

References

()

Details

./chrome/messenger/content/default/SearchDialog.xul
./chrome/messenger/content/default/SearchOptions.xul
./chrome/messenger/content/default/FilterListDialog.xul
./chrome/messenger/content/default/FilterEditor.xul
./chrome/messenger/content/default/AccountManager.xul
./chrome/messenger/content/default/accounttree.xul
./chrome/messenger/content/default/am-main.xul
./chrome/messenger/content/default/am-server-pop3.xul
./chrome/messenger/content/default/am-copies.xul
./chrome/messenger/content/default/am-advanced.xul
./chrome/messenger/content/default/aw-accounttype.xul
./chrome/messenger/content/default/aw-identity.xul
./chrome/messenger/content/default/aw-server.xul
./chrome/messenger/content/default/aw-login.xul
./chrome/messenger/content/default/aw-accname.xul
./chrome/messenger/content/default/messenger.xul
./chrome/messenger/content/default/folderPane.xul
./chrome/messenger/content/default/threadPane.xul
./chrome/messenger/content/default/subscribe.xul
./chrome/messenger/content/default/sidebar-messenger.xul

./chrome/addressbook/content/default/addressbook.xul
./chrome/addressbook/content/default/dirPane.xul
./chrome/addressbook/content/default/resultPane.xul
./chrome/addressbook/content/default/cardviewPane.xul
./chrome/addressbook/content/default/editcard.xul
./chrome/addressbook/content/default/newcardDialog.xul
./chrome/addressbook/content/default/selectaddress.xul

Please refer to the "XUL Coding Style Guidelines" in the URL above
for how to move entities into DTDs. The target deadline is M9.

Thanks!
Target Milestone: M10
We're not going to get this done by m9. CC'ing some of the relevant engineers,
who might want to either file new bugs on just their xul files, or update this
bug with their progress.
Component: XUL → Front End
Product: Browser → MailNews
Hi, Paul:

Could you help this migration?


Thanks
QA Contact: ckritzer → tao
change QA contact
I can certainly do the address book files.  I will try to help those owners of
these other files that want my help.
Blocks: 10598
Took care of the address book files (see list below).  Many of these files were
renamed in the same step where dtd files were created.

./chrome/addressbook/content/default/addressbook.xul
./chrome/addressbook/content/default/dirPane.xul
./chrome/addressbook/content/default/resultPane.xul
./chrome/addressbook/content/default/cardviewPane.xul
./chrome/addressbook/content/default/editcard.xul
./chrome/addressbook/content/default/newcardDialog.xul
./chrome/addressbook/content/default/selectaddress.xul
I've got the changes for messenger.xul, threadpane.xul and folderpane.xul in my
tree.  I'll try to checked these in tonight.
Severity: critical → blocker
Summary: Please move entities into DTDs → [BLOCKER] Please move entities into DTDs
Marking blocker for M10 since L10n has a dependency on it.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
I think all of these were done for M9.  Marking fixed.  If I'm wrong someone can
reopen.
Tao, is this done to your satisfaction?  If so, pls mark verified.  Thanks.
Status: RESOLVED → REOPENED
4 left
------
./messenger/content/default/SearchDialog.xul
./messenger/content/default/SearchOptions.xul
./messenger/content/default/FilterListDialog.xul
./messenger/content/default/FilterEditor.xul

And, this
---------
./messengercompose/content/default/MsgAttachPage.xul
Resolution: FIXED → ---
Clearing Fixed resolution due to reopen.
I have the modification for ./messengercompose/content/default/MsgAttachPage.xul in my Mac. Will check it in

when the tree will be open & green!
./messengercompose/content/default/MsgAttachPage.xul DONE
Assignee: phil → alecf
Status: REOPENED → NEW
reassigning to me to pick up the search/filter stuff
Status: NEW → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
done.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.