Open
Bug 1379141
Opened 7 years ago
Updated 2 years ago
[FirstPartyIsolation] Not able to load Alibaba.com
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
NEW
People
(Reporter: ioana.chiorean, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-backlog2])
Attachments
(1 file)
184.67 KB,
image/png
|
Details |
Prerequisites:
Create the perf ""privacy.firstparty.isolate"" and enable it
Disable the perf ""network.predictor.enabled""
Disable the perf ""network.predictor.enable-prefetch""
Disable the perf ""browser.safebrowsing.malware.enabled""
Disable the perf ""browser.safebrowsing.phishing.enabled""
Create the perf ""privacy.firstparty.isolate.restrict_opener_access"" and Enable it
Steps to reproduce:
1. Go to alibaba.com
2. Force mobile version by going to m.alibaba.com
Expected results:
- page should be loaded correctly
Actual results:
- URL address becomes about:neterror?e=unknownProtocolFound&u=enalibaba://sc-home?ck=home and we get a "The address wasn't understood"
- if we force m.alibaba.com - the page scheleton is loaded but no text noir images are displayed
Note:
- it is well displayed in desktop mode and in Chrome.
Comment 1•7 years ago
|
||
Tim, could you look into this issue?
Flags: needinfo?(tihuang)
Priority: -- → P2
Updated•7 years ago
|
Assignee: nobody → tihuang
Updated•7 years ago
|
Whiteboard: [domsecurity-active]
Updated•6 years ago
|
Assignee: tihuang → nobody
Comment 3•6 years ago
|
||
Ethan: Downgrading this from "active" since Tim's on leave; tagging you with a ni? to make sure that's OK and not urgent to find someone for it right away.
Flags: needinfo?(ettseng)
Priority: P2 → P3
Whiteboard: [domsecurity-active] → [domsecurity-backlog2]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•