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 AM Andrea Marchesini <amarches...@mozilla.com> wrote: > *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 > > *Platform coverage*: everywhere. > > *Estimated or target release*: 66 - after 1 cycle with this feature enabled > in nightly and beta only. > > *Preference behind which this will be implemented* > :dom.targetBlankNoOpener.enabled > > *Is this feature enabled by default in sandboxed iframes?* yes. > > *DevTools bug*: no special support for devtools. Maybe we could dispatch an > Intervention report via Reporting API. > > *Do other browser engines implement this?* Only safari at the moment: > https://trac.webkit.org/changeset/237144/webkit > > *web-platform-tests*: none, yet, but I can convert my mochitest in a WPT > easily. > > *Is this feature restricted to secure contexts?* no needs. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
