19573 2008-06-16 02:57:21 -0700 REGRESSION: Doctype is not parsed unless it's at the very beginning of the document (font-size didn't inherit from body to table elements) 2008-06-17 00:15:31 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Mac (Intel) OS X 10.5 RESOLVED WONTFIX P1 Normal --- 1 rbarberac webkit-unassigned ap mitz oldest_to_newest 83442 0 rbarberac 2008-06-16 02:57:21 -0700 When using body { font-size:20px; } the table elements didn't show at this size. 83443 1 21724 rbarberac 2008-06-16 02:59:18 -0700 Created attachment 21724 Case reduction All the text in this page should present the same size. It works fine in Safari 3.1.1 83482 2 mitz 2008-06-16 09:54:21 -0700 From quirks.css: /* Tables reset both line-height and white-space in quirks mode. */ /* Compatible with WinIE. Note that font-family is *not* reset. */ table { white-space: normal; line-height: normal; font-weight: normal; font-size: medium; font-variant: normal; font-style: normal; color: -webkit-text; text-align: -webkit-auto } 83490 3 rbarberac 2008-06-16 10:44:29 -0700 I don't understand the quirks mode issue. The sample is declared as HTML 4.01 strict. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> Regards 83496 4 mitz 2008-06-16 10:54:50 -0700 (In reply to comment #3) > I don't understand the quirks mode issue. The sample is declared as HTML 4.01 > strict. The DOCTYPE is not parsed. Looking at the source, I see that it begins with *two* UTF-8-encoded BOMs (EF BB BF repeated twice), and I believe the second one throws the parser off. 83526 5 ap 2008-06-16 13:08:33 -0700 Safari 3.1.1 is OK even with text garbage before the DOCTYPE (just as Firefox is), so this change is not just something caused by BOM handling changes. 83566 6 mitz 2008-06-16 22:30:22 -0700 Looks like entering quirks mode and ignoring the DOCTYPE is the right thing to do according to <http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#the-initial>. 83568 7 mitz 2008-06-16 22:40:33 -0700 ...and IE agrees with TOT: attachment 21724 is rendered the same in IE. Removing one BOM changes the rendering (so that the table text is the same size as body text) in IE and in TOT. 83570 8 ap 2008-06-16 22:55:08 -0700 After a discussion in #webkit, the consensus appears to be that we want to match IE, Opera and HTML5, not Firefox. According to HTML5, only whitespace and comments are allowed before DOCTYPE (and implicitly, a single BOM as the very first character). 83573 9 rbarberac 2008-06-16 23:33:23 -0700 Ok, I'm with you in that the correct way to handle this case is to go into quirks mode. But are there any way to know that the browser is working in quirks mode? All the <DOCTYPE> related conditions are easy to spot looking at the HTML source. But the BOM one is not, because it's an invisible-no-breaking-space character, so you need to use a hexeditor to see them. In my case, there are two developers working on a django project, one is working with TextMate in OS X and other with a windows editor (notepad+). This last one is putting a UTF-8 BOM. After that the Django development server is adding other UTF-8 BOM. But looking at the sources of the HTML with a text editor, I can't see nothing before the <DOCTYPE>. This will be a hard to spot "feature-working-as-a-bug" 83580 10 ap 2008-06-17 00:09:09 -0700 (In reply to comment #9) > But are there any way to know that the browser is working in > quirks mode? There is always alert(document.compatMode), although it is admittedly only helpful when you already suspect something like that. > But the BOM one is not, because it's an invisible-no-breaking-space character, > so you need to use a hexeditor to see them. This is very true. In some similar cases, this can even lead to security bugs, so it is particularly important to handle invisible characters to the letter of the spec, so that all browsers and security filters agree on the same behavior. 83581 11 rbarberac 2008-06-17 00:15:31 -0700 >There is always alert(document.compatMode), although it is admittedly only >helpful when you already suspect something like that. Well, after this incident I'll always suspect something like that ;-). >In some similar cases, this can even lead to security bugs, >so it is particularly important to handle invisible characters to the letter of >the spec, so that all browsers and security filters agree on the same behavior. Yes, it seems the way to go. 21724 2008-06-16 02:59:18 -0700 2008-06-16 02:59:18 -0700 Case reduction font-size.html text/html 2308 rbarberac 77u/77u/PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEvL0VOIgog ICAiaHR0cDovL3d3dy53My5vcmcvVFIvaHRtbDQvc3RyaWN0LmR0ZCI+Cgo8aHRtbCBsYW5nPSJl biI+CjxoZWFkPgoJPHRpdGxlPkZvbnQtc2l6ZSBpbiBib2R5PC90aXRsZT4KCTxzdHlsZSB0eXBl PSJ0ZXh0L2NzcyIgbWVkaWE9InNjcmVlbiI+CgkJYm9keSB7IAoJCQlmb250LXNpemU6MjRweDsg CgkJfQoJPC9zdHlsZT4KPC9oZWFkPgo8Ym9keT4KCTxwPkxvcmVtIGlwc3VtIGRvbG9yIHNpdCBh bWV0LCBjb25zZWN0ZXR1ciBhZGlwaXNpY2luZyBlbGl0LCBzZWQgZG8gZWl1c21vZCB0ZW1wb3Ig aW5jaWRpZHVudCB1dCBsYWJvcmUgZXQgZG9sb3JlIG1hZ25hIGFsaXF1YS4gVXQgZW5pbSBhZCBt aW5pbSB2ZW5pYW0sIHF1aXMgbm9zdHJ1ZCBleGVyY2l0YXRpb24gdWxsYW1jbyBsYWJvcmlzIG5p c2kgdXQgYWxpcXVpcCBleCBlYSBjb21tb2RvIGNvbnNlcXVhdC4gRHVpcyBhdXRlIGlydXJlIGRv bG9yIGluIHJlcHJlaGVuZGVyaXQgaW4gdm9sdXB0YXRlIHZlbGl0IGVzc2UgY2lsbHVtIGRvbG9y ZSBldSBmdWdpYXQgbnVsbGEgcGFyaWF0dXIuIEV4Y2VwdGV1ciBzaW50IG9jY2FlY2F0IGN1cGlk YXRhdCBub24gcHJvaWRlbnQsIHN1bnQgaW4gY3VscGEgcXVpIG9mZmljaWEgZGVzZXJ1bnQgbW9s bGl0IGFuaW0gaWQgZXN0IGxhYm9ydW0uPC9wPgkJCgk8dGFibGU+CgkJPHRyPjx0aD5Db2wgMTwv dGg+PHRoPkNvbCAyPC90aD48dGg+Q29sIDI8L3RoPjwvdHI+CgkJCgkJCTx0cj4KCQkJCTx0ZD4x MjM0NTY3ODk8L3RkPgoJCQkJPHRkPmFAYy5jb208L3RkPgoJCQkJPHRkPkxvcmVtIGlwc3VtIGRv bG9yIHNpdCBhbWV0LCBjb25zZWN0ZXR1ciBhZGlwaXNpY2luZyBlbGl0LCBzZWQgZG8gZWl1c21v ZCB0ZW1wb3IgaW5jaWRpZHVudCB1dCBsYWJvcmUgZXQgZG9sb3JlIG1hZ25hIGFsaXF1YS4gVXQg ZW5pbSBhZCBtaW5pbSB2ZW5pYW0sIHF1aXMgbm9zdHJ1ZCBleGVyY2l0YXRpb24gdWxsYW1jbyBs YWJvcmlzIG5pc2kgdXQgYWxpcXVpcCBleCBlYSBjb21tb2RvIGNvbnNlcXVhdC4gRHVpcyBhdXRl IGlydXJlIGRvbG9yIGluIHJlcHJlaGVuZGVyaXQgaW4gdm9sdXB0YXRlIHZlbGl0IGVzc2UgY2ls bHVtIGRvbG9yZSBldSBmdWdpYXQgbnVsbGEgcGFyaWF0dXIuIEV4Y2VwdGV1ciBzaW50IG9jY2Fl Y2F0IGN1cGlkYXRhdCBub24gcHJvaWRlbnQsIHN1bnQgaW4gY3VscGEgcXVpIG9mZmljaWEgZGVz ZXJ1bnQgbW9sbGl0IGFuaW0gaWQgZXN0IGxhYm9ydW0uPC90ZD4gCgkJCTwvdHI+CgkJCTx0cj4K CQkJCTx0ZD4xMjM0NTY3ODk8L3RkPgoJCQkJPHRkPmFAYy5jb208L3RkPgoJCQkJPHRkPkxvcmVt IGlwc3VtIGRvbG9yIHNpdCBhbWV0LCBjb25zZWN0ZXR1ciBhZGlwaXNpY2luZyBlbGl0LCBzZWQg ZG8gZWl1c21vZCB0ZW1wb3IgaW5jaWRpZHVudCB1dCBsYWJvcmUgZXQgZG9sb3JlIG1hZ25hIGFs aXF1YS4gVXQgZW5pbSBhZCBtaW5pbSB2ZW5pYW0sIHF1aXMgbm9zdHJ1ZCBleGVyY2l0YXRpb24g dWxsYW1jbyBsYWJvcmlzIG5pc2kgdXQgYWxpcXVpcCBleCBlYSBjb21tb2RvIGNvbnNlcXVhdC4g RHVpcyBhdXRlIGlydXJlIGRvbG9yIGluIHJlcHJlaGVuZGVyaXQgaW4gdm9sdXB0YXRlIHZlbGl0 IGVzc2UgY2lsbHVtIGRvbG9yZSBldSBmdWdpYXQgbnVsbGEgcGFyaWF0dXIuIEV4Y2VwdGV1ciBz aW50IG9jY2FlY2F0IGN1cGlkYXRhdCBub24gcHJvaWRlbnQsIHN1bnQgaW4gY3VscGEgcXVpIG9m ZmljaWEgZGVzZXJ1bnQgbW9sbGl0IGFuaW0gaWQgZXN0IGxhYm9ydW0uPC90ZD4gCgkJCTwvdHI+ CQkKCTwvdGFibGU+Cgk8cD5Mb3JlbSBpcHN1bSBkb2xvciBzaXQgYW1ldCwgY29uc2VjdGV0dXIg YWRpcGlzaWNpbmcgZWxpdCwgc2VkIGRvIGVpdXNtb2QgdGVtcG9yIGluY2lkaWR1bnQgdXQgbGFi b3JlIGV0IGRvbG9yZSBtYWduYSBhbGlxdWEuIFV0IGVuaW0gYWQgbWluaW0gdmVuaWFtLCBxdWlz IG5vc3RydWQgZXhlcmNpdGF0aW9uIHVsbGFtY28gbGFib3JpcyBuaXNpIHV0IGFsaXF1aXAgZXgg ZWEgY29tbW9kbyBjb25zZXF1YXQuIER1aXMgYXV0ZSBpcnVyZSBkb2xvciBpbiByZXByZWhlbmRl cml0IGluIHZvbHVwdGF0ZSB2ZWxpdCBlc3NlIGNpbGx1bSBkb2xvcmUgZXUgZnVnaWF0IG51bGxh IHBhcmlhdHVyLiBFeGNlcHRldXIgc2ludCBvY2NhZWNhdCBjdXBpZGF0YXQgbm9uIHByb2lkZW50 LCBzdW50IGluIGN1bHBhIHF1aSBvZmZpY2lhIGRlc2VydW50IG1vbGxpdCBhbmltIGlkIGVzdCBs YWJvcnVtLjwvcD4KPC9ib2R5Pgo8L2h0bWw+Cg==