Sending a webpage that contains frames doesn't show when reading
Categories
(MailNews Core :: MIME, defect)
Tracking
(Not tracked)
People
(Reporter: bugzilla, Unassigned)
References
Details
Attachments
(2 files)
Updated•25 years ago
|
Comment 1•25 years ago
|
||
Comment 2•25 years ago
|
||
Reporter | ||
Comment 4•23 years ago
|
||
Comment 5•23 years ago
|
||
Comment 6•22 years ago
|
||
Comment 7•21 years ago
|
||
Updated•20 years ago
|
Comment 8•17 years ago
|
||
Updated•17 years ago
|
Assignee | ||
Updated•16 years ago
|
Comment 9•5 years ago
|
||
Dossy, does this reproduce for you?
Comment 10•5 years ago
|
||
Wayne, I honestly don't even know how to "email this web page" inline as an attachment to someone using modern Chrome and TB, aside from saving the page as HTML and then attaching that HTML to the message ...
I did that with a simple test page, and TB doesn't try to render the HTML in the reader pane? Chrome won't even parse <frameset> and <frame> nodes into the DOM any more, even with a DOCTYPE of HTML 4.01 Frameset.
I'd say this more than a "wontfix" bug at this point, but a "cantfix" ...
Attaching my test .html file in case someone else wants to take a shot at this ...
Comment 11•5 years ago
|
||
Also, as plenty of sites now emit X-Frame-Options: deny
- even if we tried to render the frameset document, we may be instructed to refuse to do it by the server, anyway.
Comment 12•5 years ago
|
||
Updated•4 years ago
|
Description
•