Write test that mixed-content-auto-upgrading does not apply to `<track>` elements
Categories
(Core :: DOM: Security, task, P3)
Tracking
()
People
(Reporter: ckerschb, Assigned: tiwari.abhishektiwari23, Mentored)
References
Details
(Keywords: good-first-bug, Whiteboard: [domsecurity-backlog])
Attachments
(1 obsolete file)
Internally we match track
to type media
, though the spec for mixed content auto upgrading explicitly stated that we should only upgrade:
- image,
- audio
- video.
We should write an automated test to ensure track is not subject to mixed-content-auto-upgrading.
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Sir, I want to give a try to this bug,
Comment 2•2 years ago
|
||
Great. If you want to tackle this bug, please follow the guide at https://wiki.mozilla.org/Good_first_bug to get a working build environment and make sure you can run the test file dom/security/test/mixedcontentblocker/test_main.html#35
using ./mach test <path to test>
.
The first steps is to make a change to the test that adds a case for a <track>
element.
Feel free to reach out to me as @fbraun:mozilla.org
on Matrix (Instructions at https://wiki.mozilla.org/Matrix) for further questions.
Assignee | ||
Comment 3•2 years ago
|
||
Ok, Thanks, I will give my best
Assignee | ||
Comment 4•2 years ago
|
||
Sir, I am trying to submit a patch but getting the error Freddy is not a valid reviewer name, and I also looked for the same on Mozilla but not able to find you. Please have a look at this - https://paste.mozilla.org/tG8prCS1
Comment 5•2 years ago
|
||
That's odd. You can go without a reviewer name (though maybe "freddyb" could work).
Assignee | ||
Comment 6•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 7•1 year ago
|
||
Why should track be excluded, see: https://bugzilla.mozilla.org/show_bug.cgi?id=1439463
Comment 8•1 year ago
|
||
To clarify, we do not upgrade <track>
since https://bugzilla.mozilla.org/show_bug.cgi?id=1819898. This is just about the missing test case. I think the bug mentioned above can be closed?
Description
•