-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In editor, make "Review issues" link open in a new tab #5319
Conversation
I have to look into these test failures, which I don't think are directly related to this change:
|
It may be an issue introduced in the latest Gutenberg. I'll check it out. |
The test failure doesn't happen in Gutenberg v8.8.0. It does happen in v8.9.0. Looking into what changed. |
Using git-bisect identified the failure to be introduced by WordPress/gutenberg@7fbdda2. |
This looks like a bug with Gutenberg. It's exporting the |
Plugin builds for 54c0bde are ready 🛎️!
|
|
…) on Gutenberg v8.9.0
…rom filtering customize_loaded_components
Co-authored-by: Pierre Gordon <16200219+pierlon@users.noreply.github.com>
Co-authored-by: John Watkins <johnwatkins0@gmail.com> Co-authored-by: Pierre Gordon <16200219+pierlon@users.noreply.github.com>
Summary
This relates to #5304, but I'm not sure it fixes it.
In the editor, various incarnations of this notice display when there are AMP validation issues at the post's URL:
Previously, this would open in the same tab. Now this will open in a new tab.
Unfortunately, what we are able to do with that link is very limited, so I didn't add the usual icon to visually indicate it would open in a new tab. There is an
__unstableHTML
parameter we can add to the notice options to allow HTML strings to be passed into the notice, but the inline documentation for notices states very emphatically not to use it.For similar reasons, we have to use an onClick handler instead of href with a target attribute to open the link in a new tab.
Checklist