NOSCRIPT element does not render in Composer

RESOLVED FIXED in mozilla1.5beta



18 years ago
16 years ago


(Reporter: rubydoo123, Assigned: john)



Windows 98

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [behavior],edt_b3)



18 years ago
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

18 years ago
sample code:

<noscript><p>P element within NOSCRIPT element</p></noscript>
Keywords: correctness
Priority: -- → P4
Whiteboard: [behavior]
Target Milestone: --- → mozilla1.0

Comment 2

17 years ago
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

Comment 3

17 years ago
Daniel:  Does your work fix this bug?
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 ?


17 years ago
Target Milestone: mozilla1.0.1 → Future

Comment 5

16 years ago
nominating topembed, this may be important for a future client
Keywords: topembed

Comment 6

16 years ago
Discussed in edt.  Plussing.
Keywords: topembed → topembed+
Whiteboard: [behavior] → [behavior],edt_b3


16 years ago
QA Contact: sujay → beppe

Comment 7

16 years ago
This bug is future... Can we get an updated milestone
Target Milestone: Future → mozilla1.5beta

Comment 8

16 years ago
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

Comment 9

16 years ago
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

16 years ago
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

16 years ago
OK, it's fixed with bug 77296.
Last Resolved: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.