275113 - Firefox/Mozilla Incorrectly Displays the DotNet Edit Module HTML editor

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Loren Bosshard]

I have captured HTML Pages from the website that best shows the problem...BUT it
seems I can't attach them to this message.

On our website .... the Foxfire & Mozilla Both incorrectly displays the DOTNET
HTML Edit Moduel and the result is an un-usable display .... MS IE workks JUST
FINE .....

I'll Send a seperate Email with the samples of the displays as attachments.

Regards L.Bosshard

Comment 1

[Loren Bosshard]

Attachment: Example of the HTML Editor opened with Firefox

This is a sample of the broken HTML Editor with firefox

Comment 2

[Loren Bosshard]

Attachment: Correct EDITOR Dsiplay opened with MS IE

This is the correct format for the HTML Editor opened with MS IE 6.2

Comment 3

[Nickolay_Ponomarev]

Please provide an URL of the real page. The attached pages are not helpful.

You should find out yourself why it doesn't work in Mozilla. (that is, make sure
that the cause is not some IE-specific code you use). Bugzilla is for reporting
bugs. You can try asking for help at http://forums.mozillazine.org/ (web
development section) or in other forums.

Comment 4

[Phil Ringnalda (:philor)]

Actually, I would say that the attachments are helpful, though only in knowing
how to resolve the bug report, not in solving your problem with your site. If I
understand you correctly, those are the result of first opening the site in
Firefox and saving the page, and then opening it in IE and saving the page? If
so, the only resolution we can offer is the rather harsh INVALID. If you give
different things to us and to IE, we can't help that. (Just giving us the same
HTML you give to IE isn't likely to help much, either, since it looks like it
was written under the assumption that only IE would ever see it, but again,
that's not something we can change.)

If you find specific things that there's reason to believe we should, or try to,
support (finding mention of them in a public specification, not just in a page
at MSDN, is a good sign there), and we don't, don't hesitate to report them, but
I'm afraid that "here's some very very invalid HTML that still has some
unprocessed ASP stuff and some IE-specific things in it even though this is the
non-IE version, make it work" just isn't possible.