Closed
Bug 1399170
Opened 7 years ago
Closed 7 years ago
Write test to make sure that data: URIs work together correctly with mozbrowser
Categories
(Core :: DOM: Security, enhancement, P2)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
mozilla57
Tracking | Status | |
---|---|---|
firefox57 | --- | fixed |
People
(Reporter: ckerschb, Assigned: ckerschb)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file, 1 obsolete file)
5.04 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → ckerschb
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [domsecurity-active]
Assignee | ||
Comment 1•7 years ago
|
||
Hey Smaug, since you are already familiar with my changes, I guess it makes sense to wait till you are back from PTO.
Whenver you get a chance, could you please review this patch? Thanks.
Flags: needinfo?(bugs)
Comment 2•7 years ago
|
||
Comment on attachment 8908134 [details] [diff] [review]
bug_1399170_mozbrowser_test.patch
This is fine, but I'd like to see also a test where first non-data url is loaded to mozbrowser and then one tries to load data url
Flags: needinfo?(bugs)
Attachment #8908134 -
Flags: review+
Assignee | ||
Comment 3•7 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #2)
> This is fine, but I'd like to see also a test where first non-data url is
> loaded to mozbrowser and then one tries to load data url
I added a second test - I suppose this is what you meant, right?
Attachment #8908134 -
Attachment is obsolete: true
Attachment #8909270 -
Flags: review?(bugs)
Updated•7 years ago
|
Attachment #8909270 -
Flags: review?(bugs) → review+
Pushed by mozilla@christophkerschbaumer.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9072e9c0d0aa
Test mozbrowser can not load data URI in iframe. r=smaug
Comment 5•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox57:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
You need to log in
before you can comment on or make changes to this bug.
Description
•