Closed Bug 48535 Opened 24 years ago Closed 23 years ago

Not all of the icons appear in Show All Tags mode

Categories

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

x86
Windows 98
defect

Tracking

()

VERIFIED DUPLICATE of bug 88036
Future

People

(Reporter: rubydoo123, Assigned: glazou)

References

Details

(Whiteboard: [p:4][nsbeta3-])

Attachments

(1 file)

Either open an existing page, or create a new page in Normal mode. Make sure you 
insert a few breaks, add a couple lines of text, insert a table

Toggle to Show all tags mode, the table, tr, and br element start tags do not 
appear
adding keywords and status

I was using the build from 8/10
Keywords: correctness, nsbeta3
Priority: P3 → P4
Whiteboard: [nsbeta3+][p:4]
Target Milestone: --- → M18
Thanks, I've been meaning to file this for quite some time!
Marc: Remember, these are background images on the tags via CSS.
Any idea why these don't show up?
Assignee: cmanske → attinasi
The problem is that Composer is creating transitional docs that are rendered in 
Quirks mode, and in Quirks mode the Table and TR backgrounds are rendered as Nav 
did it, in the cells. 

If you save the document, change the doctype to strict, then reload it in 
composer and turn on Show All Tags the Table image shows. BR never shows it's 
background image or color. The TR tag is showing, but you cannot see much of it 
as the TD icon is overwriting it, but if you add enough padding to the cells and 
you can see it. 

So, given that the only real problem here is that BR cannot have a background 
image I would think that beta3+ is not really appropriate. What do the rest of 
the concerned parties think?

(Attaching a strict-mode doc to load in composer so you can see the table icon)
Status: NEW → ASSIGNED
CC'd Charley since he needs to comment in the beta3+ nature of this bug. Alos, 
clearing the beta3+ for re-evaluation...
Whiteboard: [nsbeta3+][p:4] → [p:4]
but adding strict to a doc could make it invalid html, especially if it was 
originally created using 3.2, and not putting in a doctype. It's really the 
perception of correctness to the end user, if they toggle and don't see 
something, then the impression is that something is terribly wrong. Could it be 
because of the tbody element?

The br not working is very strange, I will run my element checker again to see 
if there are other element icons that do not appear
Can we please not use the "quirks" mode in Composer? I don't know why we would
want to use it at all, actually.
Beth: I never suggested that you use a strict doctype - I was simply explaining 
why the background image was not visible for the table and tr tags. I don't 
think the tbody tag has anything to do with it, since the problem of background 
images on tables and tr elements in Quirks mode exists outside of composer 
regardless of the presence or absence of the tbody.

Charley: you can disable the Quirks mode in composer I think - I know Viewer has 
code that allows you to override the doctype and view in a specific mode, so you 
should be able to implement that in Composer too. I think there is an API on the 
PresContext to set the mode, allowing Standard, Quirks, or UseDocType (actually, 
it may be a pref, I cannot remember).
From what I can tel, there is nothing terribly serious in this bug. I think that 
the BR element not showing a background is the most serious problem and that is 
pretty minor. Sorry, denying beta3 approval :(
Whiteboard: [p:4] → [p:4][nsbeta3-]
Target Milestone: M18 → Future
*** Bug 58253 has been marked as a duplicate of this bug. ***
*** Bug 82465 has been marked as a duplicate of this bug. ***
Here is a list of tags that are missing (from previous dup bug):
APPLET
AREA
BASEFONT
BR
COL
COLGROUP
HR
NOSCRIPT (submitting additional bug that it does not render at all)
OPTION
OPTGROUP
PARAM
SCRIPT
TABLE
TBODY
TFOOT
THEAD
TR
reassigning to myself
Assignee: attinasi → glazman
Status: ASSIGNED → NEW

*** This bug has been marked as a duplicate of 88036 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.