Closed
Bug 463923
Opened 16 years ago
Closed 16 years ago
show expanded technical details in expert mode (SSL error pages)
Categories
(Core Graveyard :: Security: UI, enhancement)
Core Graveyard
Security: UI
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.9.2a1
People
(Reporter: maxxmozilla, Assigned: maxxmozilla)
Details
(Keywords: verified1.9.1)
Attachments
(2 files, 1 obsolete file)
3.68 KB,
patch
|
johnath
:
review+
Gavin
:
review+
beltzner
:
approval1.9.1+
beltzner
:
approval1.9.1b2-
|
Details | Diff | Splinter Review |
79.33 KB,
image/png
|
Details |
follow-up from Bug 431826
Assignee | ||
Comment 1•16 years ago
|
||
Attachment #347180 -
Flags: review?(gavin.sharp)
Comment 2•16 years ago
|
||
I think you want review from johnath, since you're changing his code and UI.
Assignee | ||
Comment 3•16 years ago
|
||
I've thought about this but he is not listed as a peer :| ?
http://www.mozilla.org/owners.html
(also gavin e-mail looks to be not current)
Comment 4•16 years ago
|
||
It's current, it's just not the one I use for Bugzilla. Johnathan can (and probably should) review changes to that code. Looks fine to me, though.
Assignee | ||
Updated•16 years ago
|
Attachment #347180 -
Flags: review?(gavin.sharp) → review?(johnath)
Comment 5•16 years ago
|
||
bug 431826 included a browser-chrome test which tests the behaviour of the expert pref to ensure that we don't break it at some point in the future. You probably don't need to concoct a whole new test here, but can you add this check to the existing test? If some future do-gooder changes the structure of this page and breaks the "technicalContent" ID, it would be nice to catch it.
Thanks for the patch though, the code change looks fine.
Assignee | ||
Comment 6•16 years ago
|
||
Changes:
- removes second toggle from expert + technical link case...
- updates the test
Attachment #347180 -
Attachment is obsolete: true
Attachment #347322 -
Flags: review?(johnath)
Attachment #347180 -
Flags: review?(johnath)
Comment 7•16 years ago
|
||
Comment on attachment 347322 [details] [diff] [review]
Fix v2
Looks good to me. You may need an actual browser peer in order to get approval to land this, but thanks again for the work.
Attachment #347322 -
Flags: review?(johnath) → review+
Assignee | ||
Comment 8•16 years ago
|
||
Comment on attachment 347322 [details] [diff] [review]
Fix v2
Asking for official approval.
Attachment #347322 -
Flags: review?(gavin.sharp)
Updated•16 years ago
|
Attachment #347322 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Updated•16 years ago
|
Keywords: checkin-needed
Comment 9•16 years ago
|
||
you've got review, but if you want this to be checkin-needed, it will need explicit approval for landing, now that we are in beta freeze. You can request approval1.9.1b2 on the patch, and one of the beta drivers will evaluate it.
Sorry, I know this process can seem burdensome, but when we're locking down for a release, we are deliberately... more burdensome. :)
Updated•16 years ago
|
Keywords: checkin-needed
Updated•16 years ago
|
Attachment #347322 -
Flags: approval1.9.1b2?
Updated•16 years ago
|
Attachment #347322 -
Flags: approval1.9.1b2? → approval1.9.1b2-
Comment 10•16 years ago
|
||
Comment on attachment 347322 [details] [diff] [review]
Fix v2
We'll wait until after beta for this.
Comment 11•16 years ago
|
||
Comment on attachment 347322 [details] [diff] [review]
Fix v2
a191=beltzner
Attachment #347322 -
Flags: approval1.9.1+
Assignee | ||
Updated•16 years ago
|
Keywords: checkin-needed
Comment 12•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: needs trunk baking
Target Milestone: --- → mozilla1.9.2a1
Updated•16 years ago
|
Flags: in-testsuite+
Comment 13•16 years ago
|
||
Keywords: checkin-needed → fixed1.9.1
Whiteboard: needs trunk baking
Backed out of 1.9.1 to fix test failures:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.1/1228955981.1228960442.2915.gz#err0
Keywords: fixed1.9.1
Comment 15•16 years ago
|
||
Were the tests failing reliably? Why isn't it failing on the trunk? If it's just an unreliable test we should disable the test, not back out the entire patch.
The tests were failing constantly, although only on one Mac test box, and backing out the patch fixed the failure.
You may be right that it's not the patch's fault, but the sheriff doesn't have to be the one to figure that out.
Comment 17•16 years ago
|
||
Note that bug 416661 seemingly had the same issue.
Assignee | ||
Comment 18•16 years ago
|
||
Should I attach a patch without the test or there would be some investigation why mac test box is failing the test ?
Comment 19•16 years ago
|
||
It sounds like that tinderbox is just broken somehow. Someone should try relanding the patch, and if it acts up again they can just disable the test.
Keywords: checkin-needed
Comment 20•16 years ago
|
||
Keywords: checkin-needed → fixed1.9.1
Comment 21•16 years ago
|
||
verified fixed on the 1.9.1 branch using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20081223 Shiretoko/3.1b3pre and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081223 Shiretoko/3.1b3pre.
verified fixed on the trunk using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20081223 Minefield/3.2a1pre and Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20081223 Minefield/3.2a1pre
We should update the existing Litmus test case so nominating for that as well.
Comment 22•16 years ago
|
||
Comment 23•16 years ago
|
||
Test case added for the overall look and feel of the error page.
https://litmus.mozilla.org/show_test.cgi?id=7742
Flags: in-litmus? → in-litmus+
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•