Closed
Bug 517746
Opened 15 years ago
Closed 15 years ago
Fix XHTML validation errors on the Community, Foundation, and Projects sections
Categories
(www.mozilla.org :: General, defect)
www.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rowno, Assigned: rowno)
Details
(Keywords: xhtml)
Attachments
(1 file, 2 obsolete files)
This patch fixes most of the HTML validation errors on the Community and Projects sections of the site.
Assignee | ||
Comment 1•15 years ago
|
||
Attachment #401684 -
Attachment is obsolete: true
Comment 2•15 years ago
|
||
Roland, thanks for making those tweaks to the patch. I just reviewed this and have a few comments:
* I'd include community/gen-ng-info as part of the patch for changes generated pages. The person who owns that is different than from the straight HTML files.
* Should we be changing '&' signs in URLs to '&'? I spotted checked some of these and some worked fine, but one returned different pages. Compare:
http://www.google.com/search?q=Mozilla&ie=UTF-8&oe=UTF-8&hl=zh-TW&lr=lang_zh-TW
http://www.google.com/search?q=Mozilla&ie=UTF-8&oe=UTF-8&hl=zh-TW&lr=lang_zh-TW
* In the projects/powered-by.html page there's a space in the link to <a href="/about/manifesto "> that I suppose we should remove.
Assignee | ||
Comment 3•15 years ago
|
||
My bad, I forgot to exclude the gen-ng-info file from the patch. And yes, we should be changing '&' signs to '&' because otherwise the xml parser tries to read & and the characters following as html entities.
I'll submit a fixed version of the patch later today.
Comment 4•15 years ago
|
||
If changing the & signs in URLs changes where those links go, perhaps we need to allow those pages to not validate?
Comment 5•15 years ago
|
||
Comment on attachment 402561 [details] [diff] [review]
Updated the patch and excluded generated pages
>+<p><span style="text-decoration:underline">Best Viewed With Buttons</span>.
>+<p><span style="text-decoration:underline">Site Icons (favicons)</span>. If you
>+<p><span style="text-decoration:underline">High Resolution Copies</span>. We
Is there some CSS class we can use instead of something like this? If not, I prefer the form |style="text-decoration: underline;"|.
r=me with that.
Attachment #402561 -
Flags: review+
Comment 6•15 years ago
|
||
(In reply to comment #4)
> If changing the & signs in URLs changes where those links go, perhaps we need
> to allow those pages to not validate?
No, he's changing them so that they will be correct.
Status: NEW → ASSIGNED
Comment 7•15 years ago
|
||
Did you try out the two links mentioned in comment #2? The existing link from community/intl/zh.html goes to a Google results page localized in zh-TW. The one from the patch goes to a search result in English.
Google doesn't seem to be processing the & part of the URL the same way as the &. In fact, it seems to be ignoring everything after the first & since the results page looks like same as:
http://www.google.com/search?q=Mozilla
Comment 8•15 years ago
|
||
(In reply to comment #7)
> Did you try out the two links mentioned in comment #2? The existing link from
> community/intl/zh.html goes to a Google results page localized in zh-TW. The
> one from the patch goes to a search result in English.
Take a look at the source code for that comment on this bug:
=============================
* Should we be changing '&' signs in URLs to '&amp;'? I spotted checked some
of these and some worked fine, but one returned different pages. Compare:
<a href="http://www.google.com/search?q=Mozilla&ie=UTF-8&oe=UTF-8&hl=zh-TW&lr=lang_zh-TW">http://www.google.com/search?q=Mozilla&ie=UTF-8&oe=UTF-8&hl=zh-TW&lr=lang_zh-TW</a>
<a href="http://www.google.com/search?q=Mozilla&amp;ie=UTF-8&amp;oe=UTF-8&amp;hl=zh-TW&amp;lr=lang_zh-TW">http://www.google.com/search?q=Mozilla&amp;ie=UTF-8&amp;oe=UTF-8&amp;hl=zh-TW&amp;lr=lang_zh-TW</a>
=============================
What you actually see versus what is actually used are two very different things. ;)
Comment 9•15 years ago
|
||
Ah, I understand. OK, nevermind :)
Assignee | ||
Comment 10•15 years ago
|
||
Attachment #402561 -
Attachment is obsolete: true
Comment 11•15 years ago
|
||
(In reply to comment #2)
> * I'd include community/gen-ng-info as part of the patch for changes generated
> pages. The person who owns that is different than from the straight HTML
> files.
Where are you putting this patch now? I can review it, too.
Assignee | ||
Comment 12•15 years ago
|
||
(In reply to comment #11)
> (In reply to comment #2)
> > * I'd include community/gen-ng-info as part of the patch for changes generated
> > pages. The person who owns that is different than from the straight HTML
> > files.
>
> Where are you putting this patch now? I can review it, too.
I removed the community/gen-ng-info and community/developer-forums.html files from this patch because bug #514619 already has a patch attached to it that contains these files with the same changes.
Updated•15 years ago
|
Summary: Patch for HTML errors on the Community and Projects sections → Fix XHTML validation errors on the Community, Foundation, and Projects sections
Comment 13•15 years ago
|
||
Thanks for the patch!
r52330
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•