using build from 2001052304 on win98 the NOSCRIPT element does not render in Composer: Normal & Show All Tags mode all elements should render in Composer for editing
sample code: <noscript><p>P element within NOSCRIPT element</p></noscript>
Priority: -- → P4
Target Milestone: --- → mozilla1.0
Bulk move of mozilla1.0 bugs to mozilla.1.0.1. I will try to pull some of these back in if I can.
Target Milestone: mozilla1.0 → mozilla1.0.1
Daniel: Does your work fix this bug?
nominating topembed, this may be important for a future client
Discussed in edt. Plussing.
Keywords: topembed → topembed+
Whiteboard: [behavior] → [behavior],edt_b3
This bug is future... Can we get an updated milestone
I can probably fix this along with bug 77296 if we can get the information about whether this is an editor during the parsing stage. We may have to rely on a pref for that or something.
Assignee: kin → jkeiser
Depends on: 77296
I don't know if you want to check at the parsing stage ... any docshell/browser window can be dynamically switched to editable ... composer works by loading the file like a browser, and then listening for the load to finish, and then it flips the editor bit on the window/docshell.
OK, this *should* be fixed with the patch for bug 77296, but I can't verify right now, something I did a few days ago blew away my ability to run mozilla proper. It should be in tomorrow's nightly (20030626xx), can someone test?
OK, it's fixed with bug 77296.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.