WICG isolation issues - Githubissues

WICG / isolation

Other

5 stars 7 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Is this repository still active?

#18 marcoscaceres opened 5 years ago
2
Fix some formatting.

#17 noncombatant closed 6 years ago
1
Issue 6 "the isolate-me HTTP header needs to be sent and/or processed before the Set-Cookie header" does not seem to be necessary

#16 jmanico opened 6 years ago
0
Don't assume that OS processes are the only workable security model

#15 pcwalton opened 7 years ago
0
Consider sanitizing DOM-based XSS vectors

#14 estark37 opened 7 years ago
0
Can isolated sites prevent cookie-stuffing and cookie-fixation attacks?

#13 estark37 opened 7 years ago
0
Prevent setting `document.domain`

#12 mikewest closed 7 years ago
1
Threat model and same-origin resources

#11 annevk opened 7 years ago
1
Examples use very-important.com and very-important.example.com

#10 annevk closed 7 years ago
2
All storage needs to be double-keyed, not just cookies

#9 estark37 opened 7 years ago
0
Isolation opt-out

#8 randomdross opened 7 years ago
4
Forcing strict same-site cookies prevents allowing top-level navigation

#7 davidillsley opened 7 years ago
0
Figure out issues around isolated and non-isolated content on the same origin

#6 estark37 opened 7 years ago
1
Should the spec define what the UI experience is?

#5 estark37 opened 7 years ago
9
Does per-site process isolation as implemented today address UXSS?

#4 estark37 closed 7 years ago
2
Turn off `document.domain` for isolated origins

#3 estark37 opened 7 years ago
0
Consider opt in/out for referrer headers

#2 jonathanKingston closed 7 years ago
2
Plan for isolating storage

#1 jonathanKingston opened 7 years ago
7