Closed Bug 198468 Opened 22 years ago Closed 14 years ago

Suppressed <OBJECT> tags do not display at all on the "HTML Tags" and "Preview" pages

Categories

(SeaMonkey :: Composer, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mcow, Unassigned)

Details

(Keywords: helpwanted)

Attachments

(1 file)

User-Agent: Opera/6.06 (Windows 2000; U) [en] Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 Bug 88956 was fixed to suppress rendering of plugin content. Now that this is in place, when switching to the 'HTML Tags' (aka Show All Tags) tab, there is no <OBJECT> tag shown. Tag still available in Source editing. Reproducible: Always Steps to Reproduce: 1. In Composer, open file containing, for instance, a Java <OBJECT> 2. Switch to HTML Tags page. 3. Switch to Preview page Actual Results: 1. <OBJECT> is not rendered. 2. <OBJECT> is not rendered, nor is the yellow [OBJECT] tag-flag displayed 3. <OBJECT> is not rendered Expected Results: 1. As expected 2. Expect the applet not to render, but expect the yellow tag-flag to be displayed. 3. Expect the applet to be rendered, just as in the browser.
Sample contains two <OBJECT> tags: the Java object behaves as described, while the PNG object behaves as expected -- altho the PNG object is also rendered in WYSIWYG and HTMLTags modes, also as expected.
Based on a discussion in the newsgroups, I suggest that some sort of placeholder (graphic?) be used in HTML Tags view, (perhaps Normal view, too?) to indicate non-visible elements such as suppressed plugins, <script>s, maybe <iframe>s.
Severity: normal → enhancement
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Keywords: helpwanted
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: --- → Future
Product: Browser → Seamonkey
Assignee: composer → nobody
Status: ASSIGNED → NEW
QA Contact: chrispetersen → composer
Target Milestone: Future → ---
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: