Closed
Bug 322996
Opened 19 years ago
Closed 19 years ago
Enable IDN for .is domain
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
FIXED
mozilla1.8.1
People
(Reporter: gerv, Assigned: gerv)
References
()
Details
(Keywords: fixed1.8.0.1, fixed1.8.1)
Attachments
(1 file)
819 bytes,
patch
|
mtschrep
:
approval1.8.0.1+
mtschrep
:
approval1.8.1+
|
Details | Diff | Splinter Review |
We need to enable IDN for the .is (Iceland) domain. Policy: http://www.isnic.is/english/domain/rules.php (section 1.1.1) Gerv
Assignee | ||
Comment 1•19 years ago
|
||
Here's the patch. Policy change rather than code change of any significance, so review not needed (by precedent). Gerv
Attachment #208151 -
Flags: approval1.8.0.1?
Updated•19 years ago
|
Version: Trunk → 1.8 Branch
Updated•19 years ago
|
Attachment #208151 -
Flags: approval1.8.1?
Comment 2•19 years ago
|
||
gerv requests that this be checked-in by somebody as soon as it has the necessary approvals.
Comment 3•19 years ago
|
||
Comment on attachment 208151 [details] [diff] [review] Patch v.1 Please land on trunk first - which means this change can't really make this branch until the 1.8.0.2 (I've already nominated it for that branch).
Attachment #208151 -
Flags: approval1.8.0.2?
Attachment #208151 -
Flags: approval1.8.0.1?
Attachment #208151 -
Flags: approval1.8.0.1-
Comment 4•19 years ago
|
||
This is a policy decision, it just involves adding the TLD to the "accept" list: it's not something that will cause regressions, so trunk baking time won't make a difference.
Comment 5•19 years ago
|
||
(In reply to comment #3) > (From update of attachment 208151 [details] [diff] [review] [edit]) > Please land on trunk first - which means this change can't really make this > branch until the 1.8.0.2 (I've already nominated it for that branch). Why does it have to be landed on the trunk first? This statement has no precedent for policy changes such as this. Other policy change bugs dealing with IDN (such as bug 308334 and bug 313490) were checked into the trunk and branch at the same time. I don't see why this bug cannot be the same way.
Comment 6•19 years ago
|
||
Comment on attachment 208151 [details] [diff] [review] Patch v.1 Since we allowed this without backing (bug 308334 - thanks Reed) we should do so here. Even though it's a policy decision it is being implemented in code. Typos in all.js could cause other problems (although this change is trivial to inspect). 1.8.0.1 is automatically given to users - hence a little paranoia about quality. :-)
Attachment #208151 -
Flags: approval1.8.0.1- → approval1.8.0.1+
Updated•19 years ago
|
Attachment #208151 -
Flags: approval1.8.1? → approval1.8.1+
Comment 7•19 years ago
|
||
Forgot to ask that it be landed on trunk, 1.8, and 1.8.0 branches.
Updated•19 years ago
|
Attachment #208151 -
Flags: approval1.8.0.2?
Comment 8•19 years ago
|
||
Landed on the 1.8 and 1.8.0 branches. mozilla/modules/libpref/src/init/all.js; new revision: 3.585.2.19; mozilla/modules/libpref/src/init/all.js; new revision: 3.585.2.17.2.2;
Keywords: fixed1.8.0.1,
fixed1.8.1
Target Milestone: --- → mozilla1.8.1
Comment 9•19 years ago
|
||
And on the trunk. mozilla/modules/libpref/src/init/all.js; new revision: 3.619;
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 10•19 years ago
|
||
Gavin, Reed, Mike: thanks for helping this squeeze in under the wire :-) Gerv
You need to log in
before you can comment on or make changes to this bug.
Description
•