Re: [fetch] should navigation requests really be same-origin or no-cors? (#101)

Umm...
I didn't noticed this change. https://github.com/whatwg/fetch/commit/44c2846340247a53af1b55b38f183fe76aba3fc7
This change removed "10. If response's final url flag is unset, set response's url to request's url." from "4 Fetching" section.

After this change, iii. and iv. should be 
 iii. When the user opens "https://www.example.com/scope/in_scope_sw_redirect".
    The URL bar of the pege is changed to "https://www.example.com/scope/dir/destination".
    The page sends a fetch request "https://www.example.com/scope/dir/image.png" via the Service Worker.

 iv. When the user opens "https://www.example.com/scope/out_scope_sw_redirect".
    The URL bar of the pege is changed to "https://www.example.com/out_scope/destination".
    The page will not be controlled by the Service Worker. (right??)
    The page sends a fetch request "https://www.example.com/out_scope/image.png" which is not handled by the Service Worker. (right??)

Is this an intended behavior change?
Or is my understanding incorrect?



---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/101#issuecomment-128245877