Summary: | Markup in <title> prevents decoder from looking for a charset | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> | ||||||
Component: | Layout and Rendering | Assignee: | Darin Adler <darin> | ||||||
Status: | VERIFIED FIXED | ||||||||
Severity: | Normal | ||||||||
Priority: | P2 | ||||||||
Version: | 420+ | ||||||||
Hardware: | Mac | ||||||||
OS: | All | ||||||||
Attachments: |
|
Description
Alexey Proskuryakov
2005-08-21 12:38:57 PDT
Created attachment 3493 [details]
Test case
Created attachment 3494 [details]
Proposed patch
Comment on attachment 3494 [details]
Proposed patch
I would call the variable just "inTitle" rather than "areInTitle", but
otherwise looks good. r=me
The reason why I didn't call it "inTitle" is that "in", "out" and "io" are prefixes widely used in Mac OS APIs to distinguish input and output parameters. Understood, but I don't think that convention is relevant in a large cross-platform code base that never uses that convention at all. Maybe withinTitle would be best. (Sorry I didn't land this earlier. It was marked UNCONFIRMED so it was not showing up in my query.) Sure, I really have no problem with most coding conventions :) And withinTitle looks like the best variant. Would you like me to update the patch? It's would be fine, but I can also just update the name when landing the patch. |