On Thu, Nov 22, 2018 at 6:00 PM Ehsan Akhgari wrote:
> Do you mean adding a rel attribute to ? Not sure if all of the other
> link type values for rel make sense for but having some way of
> passing "noopener" (and "opener" for that matter) directives for is
> indeed something that we should
On Thu, Nov 22, 2018 at 10:55 AM Boris Zbarsky wrote:
> On 11/22/18 1:06 AM, Ehsan Akhgari wrote:
> >> Can one do noreferrer with window.open()?
> >>
> >
> > Yes, by passing 'noopener' in the features argument:
> >
>
On 11/22/18 1:06 AM, Ehsan Akhgari wrote:
Can one do noreferrer with window.open()?
Yes, by passing 'noopener' in the features argument:
https://html.spec.whatwg.org/multipage/window-object.html#apis-for-creating-and-navigating-browsing-contexts-by-name:disowned-its-opener
But we're trying
On Thu, Nov 22, 2018 at 7:07 AM Ehsan Akhgari wrote:
> I wonder if it makes sense to make a similar change here, to make target="_blank"> imply noopener behaviour and then if that proves to be Web
> compatible, propose to change the spec to pass false there?
Yeah, I think we should try to keep
On Wed, Nov 21, 2018 at 11:55 PM Boris Zbarsky wrote:
> On 11/21/18 11:50 PM, Ehsan Akhgari wrote:
> > Would it be OK if the answer to that question be "use window.open()"?
>
> Can one do noreferrer with window.open()?
>
Yes, by passing 'noopener' in the features argument:
On 11/21/18 11:50 PM, Ehsan Akhgari wrote:
Would it be OK if the answer to that question be "use window.open()"?
Can one do noreferrer with window.open()?
Also, if your thing doing the navigation is a , not , then
window.open is pretty hard to use for that. Then again, target="_blank"> is
On Wed, Nov 21, 2018 at 3:55 PM Boris Zbarsky wrote:
> On 11/21/18 2:22 PM, Daniel Veditz wrote:
> > "opener" doesn't exist
>
> It does in WebKit's proposed changes and in our implementation of them.
>
> > You'd specify a target
> > name other than "_blank" to indicate it's a context you care
On 11/21/18 2:22 PM, Daniel Veditz wrote:
"opener" doesn't exist
It does in WebKit's proposed changes and in our implementation of them.
You'd specify a target
name other than "_blank" to indicate it's a context you care about
This seems backwards. What matters is whether the context
On Wed, Nov 21, 2018 at 7:08 AM Alex Gaynor wrote:
> Do we have any sense of how large the breakage will be, and do we have any
> docs for developers who are impacted? (I assume rel=opener is the fix?)
>
"opener" doesn't exist, and we shouldn't need it. You'd specify a target
name other than
On Wed, Nov 21, 2018 at 4:08 PM Alex Gaynor wrote:
> Do we have any sense of how large the breakage will be, and do we have any
> docs for developers who are impacted? (I assume rel=opener is the fix?)
The "fix" would be to use target=someuniquename.
And I don't think there's data, other than
I'm very excited about this -- in my experience very few developers know
about the dangers of target=_blank.
Do we have any sense of how large the breakage will be, and do we have any
docs for developers who are impacted? (I assume rel=opener is the fix?)
Yay!
Alex
On Wed, Nov 21, 2018 at 3:29
*Summary*: WebKit is experimenting an interesting feature: target=_blank on
anchor and area elements implies ref=noopener.
https://trac.webkit.org/changeset/237144/webkit/
*Bug*: https://bugzilla.mozilla.org/show_bug.cgi?id=1503681
*Link to standard*: https://github.com/whatwg/html/issues/4078
12 matches
Mail list logo
