Closed Bug 291475 Opened 20 years ago Closed 18 years ago

started adding <tbody> tags to tables on all pages

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED INVALID

People

(Reporter: kylestyle, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

The font became bigger and bold on a page I was browsing. I viewed the same page
in internet explorer and the font looked normal(not bigger and bold). I viewed
the source html from the page in firefox and there were <tbody> tags on all
tables where the font was different. I viewed the source in IE and the <tbody>
tags weren't there. I did a google search about this, in firefox. The results
from the search came back big and bold. I view the source of the google search
page and <tbody> tags where added to all of the tables on that page. Did the
same google search in IE and the <tbody> tags were not there. I had 8 or 9 tabs
open in firefox at the time so I viewed various pages in each tab and the same
thing was happenning on all of them, tags were added and the font was bigger and
bold. I close firefox and started it again. I went to the same pages and the
tags were no longer being added and the font wasn't bigger and bold anymore.

Reproducible: Couldn't Reproduce




Using Whitehart 0.1.0 theme
Does this happend in safe mode as well?
I may be out of my depth, but I suggest that: This is by design, since the DOM 
tree requires a tbody element in a table.

See Bug 164906 "view selection source shows generated code instead of 
actual source"
no reply from reporter --> invalid

Please reopen when y ou answer the question in comment 1 and have clearer steps
on how to reproduce
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Come on Jose, at the bottom ot the post it says "Couldn't reproduce".
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
(In reply to comment #0)
> The font became bigger and bold on a page I was browsing. I viewed the same page
> in internet explorer and the font looked normal(not bigger and bold).

What url is this?

> I viewed
> the source html from the page in firefox and there were <tbody> tags on all
> tables where the font was different. I viewed the source in IE and the <tbody>
> tags weren't there. 

This is by design, see comment 2
No reply from reporter --> invalid

Do not reopen unless you can answer comment 1 and comment 5
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → INVALID
#1
COULDN'T REPRODUCE, at all including safe mode.

#5
>I had 8 or 9 tabs
>open in firefox at the time so I viewed various pages in each tab and the same
>thing was happenning on all of them, tags were added and the font was bigger and
>bold.

There were 8 or 9 URLs this was happening to Google, Yahoo, MSN, and others it
didn't appear to be related to a specific site.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Although the tbody may be added by design they normally don't show up when
viewing the source. They aren't being added if I view the source now, check the
source of a page you are looking at and see if they are being added. Also,
adding them shouldn't change the appearence of a page. I suspect the tags were
just a symptom of the problem not the cause.
The first site I noticed this on was an internal site on my company network. I
have viewed it before and since without this problem and the site hasn't been
modified much before or since.
Assignee: bross2 → nobody
Since you couldn't reproduce this, it's likely a problem with your profile, potentially an extension. I'm resolving this bug as INVALID again. If you see this issue using Firefox 2.0.0.3 or later with a fresh profile, please file a new bug with detailed steps to reproduce as well as a testcase.

http://kb.mozillazine.org/Profile_Manager
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.