82472 - NOSCRIPT element does not render in Composer

Status: RESOLVED FIXED

(Core :: DOM: Editor, defect, P4)

Description

[rubydoo123]

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

Comment 1

[rubydoo123]

sample code:

<noscript><p>P element within NOSCRIPT element</p></noscript>

Comment 2

[kinmoz]

Bulk move of mozilla1.0 bugs to mozilla.1.0.1. I will try to pull some of these
back in if I can.

Comment 3

[Kathleen :Brade]

Daniel:  Does your work fix this bug?

Comment 4

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

No it does not, this is independant of my work done for AllTags mode because the
current bug is also in Normal View...

I have tried to add noscript { display: block} to EditorContent.css

The noscript elements become visible BUT the contents of the element are
a text node. Harish says that this is normal behavior when Javascript is enabled.
Any idea on how to solve this sub-issue ?

Comment 5

[saari (gone)]

nominating topembed, this may be important for a future client

Comment 6

[Michael Buckland]

Discussed in edt.  Plussing.

Comment 7

[Michael Dunn]

This bug is future... Can we get an updated milestone

Comment 8

[John Keiser (jkeiser)]

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.

Comment 9

[kinmoz]

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.

Comment 10

[John Keiser (jkeiser)]

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?

Comment 11

[John Keiser (jkeiser)]

OK, it's fixed with bug 77296.