Open
Bug 438562
Opened 16 years ago
Updated 2 years ago
Bad html in localizable string
Categories
(Thunderbird :: Security, defect)
Thunderbird
Security
Tracking
(Not tracked)
ASSIGNED
People
(Reporter: hendrik, Assigned: hendrik)
References
Details
(Whiteboard: [patchlove][blocked on bug 442189])
Attachments
(1 file, 1 obsolete file)
5.68 KB,
patch
|
philor
:
review-
|
Details | Diff | Splinter Review |
The entity CantDecryptBody uses bad html. See fix in patch.
Attachment #324609 -
Flags: review?(dmose)
Comment 1•16 years ago
|
||
Is <br /> valid in text/html documents? We're not in XHTML here. Also, what problem are you trying to solve?
Comment 2•16 years ago
|
||
<br / is a NET-enabling start tag; in HTML br is an empty element; <br /> is therefore exactly equal to <br>>, but it's used in Appendix C uses of XHTML-as-HTML because the (incorrect) error handling of browsers treats it as a br element with a minimized attribute named /, which is an invalid attribute name so it's ignored. This patch doesn't solve any problem, it's fetishism. The existing string is perfectly correct HTML, the proposed version is incorrect and depends on unspecified error handling. The only thing that would be a "fix" here would be to recast the string (probably into several separate strings) so that no markup is required within the localizable string: *that* would be worth doing, and would serve a purpose.
Comment 3•16 years ago
|
||
Comment on attachment 324609 [details] [diff] [review] fix the html r- on the grounds described by Phil
Attachment #324609 -
Flags: review?(dmose) → review-
Assignee | ||
Comment 4•16 years ago
|
||
Comment on attachment 324609 [details] [diff] [review] fix the html Thanks for clearing me up on that. Actually, I like being called a fetishist, it’s how I call myself on my website when talking about Unicode :-) Anyway, I’ll take your comments and try to split the string up in parts.
Attachment #324609 -
Attachment is obsolete: true
Assignee | ||
Comment 5•16 years ago
|
||
First try: I split up the string and put all the html tags in the corresponding js file. How’s this? I am unsure about the names, I should probably use something more descriptive, but please confirm that the idea is correct!
Attachment #326112 -
Flags: review?
Assignee | ||
Updated•16 years ago
|
Attachment #326112 -
Flags: review? → review?(dmose)
Comment 6•16 years ago
|
||
Comment on attachment 326112 [details] [diff] [review] split up string I'm gonna hand this back to Phil, as my review queue is pretty deep, so it's likely to be a while before I'd have time to get to this.
Attachment #326112 -
Flags: review?(dmose) → review?(philringnalda)
Comment 7•16 years ago
|
||
Comment on attachment 326112 [details] [diff] [review] split up string Nice tangle: the only reason you can get away with changing the strings in /suite/ without needing to change any JS for them is that bug 284369 screwed up and landed the strings for SeaMonkey without actually letting it use them; bug 442189 is currently fixing that (and some other missing parts), so once that "fixes" it, then you can *fix* it. (And when you do, please put a full stop at the end of CantDecryptBody1, and fix up the "NOTE To translater" to be a proper LOCALIZATION NOTE that doesn't talk about not translating HTML that isn't there anymore.)
Attachment #326112 -
Flags: review?(philringnalda) → review-
Assignee | ||
Comment 8•16 years ago
|
||
(In reply to comment #7) > (From update of attachment 326112 [details] [diff] [review]) > Nice tangle: the only reason you can get away with changing the strings in > /suite/ without needing to change any JS for them is that bug 284369 screwed up > and landed the strings for SeaMonkey without actually letting it use them; bug > 442189 is currently fixing that (and some other missing parts), so once that > "fixes" it, then you can *fix* it. Hm, I don’t get it. Note that I am a real beginner in JS and this was just my educated guess at how it would work. I’ll try to contact people over IRC the next time I work on this. Ah, do you mean the file msgHdrViewSMIMEOverlay.js is absent in suite? OK, but that means I’d only have to copy what I did there to the upcoming new one, right? So I wait for bug 442189. > (And when you do, please put a full stop at the end of CantDecryptBody1, and > fix up the "NOTE To translater" to be a proper LOCALIZATION NOTE that doesn't > talk about not translating HTML that isn't there anymore.) Oops, ok.
Comment 9•16 years ago
|
||
Yeah, except it's even more confusing than that: things that are in mail/ are only built by Thunderbird, things that are in suite/ are only built by SeaMonkey, but things that are in mailnews/ may be built by both, or may be only built by SeaMonkey, like http://mxr.mozilla.org/mozilla/source/mailnews/extensions/smime/resources/content/msgHdrViewSMIMEOverlay.js is.
Updated•10 years ago
|
Whiteboard: [patchlove][blocked on bug 442189]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•