You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my testing, when publishing a post from mobile that will open in a new tab, the resulting link in the published post does not have any rel values:
<a href="alink.com" target="_blank">
whereas publishing a post from web does have "noopener" and "noreferrer" rel values, even if the user inputs no rel values when editing the image link (can only add custom rel values from the web currently):
This issue began occurring because of a recent change that the web side made to stop displaying "noopener" and "noreferrer" rel attributes to the user (issuePR). In particular, the addition of "noopener" and "noreferrer" rel attributes was removed from image blocks. The reason behind this change according to the related issue was just to avoid displaying these two rel values to the user. This fix appears to work fine on web in my testing because a post published from web has those values in the html for the relevant link, but when a post is published from mobile I'm not seeing those rel values in the html of the published post.
Needs Verification
The behavior I am observing seems very odd because, in my testing, both mobile and web are saving the same attributes for the block (and even have the same output from the save function), but they're resulting in a different output in the published post. This makes me suspicious that there could be an issue with my testing (although I've reproduced this issue multiple times). If someone else has trouble reproducing this issue, then it seems very possible that there may just be something weird going on with my testing setup.
The text was updated successfully, but these errors were encountered:
Summary
In my testing, when publishing a post from mobile that will open in a new tab, the resulting link in the published post does not have any
rel
values:whereas publishing a post from web does have "noopener" and "noreferrer" rel values, even if the user inputs no rel values when editing the image link (can only add custom rel values from the web currently):
Background
This issue began occurring because of a recent change that the web side made to stop displaying "noopener" and "noreferrer" rel attributes to the user (issue PR). In particular, the addition of "noopener" and "noreferrer" rel attributes was removed from image blocks. The reason behind this change according to the related issue was just to avoid displaying these two rel values to the user. This fix appears to work fine on web in my testing because a post published from web has those values in the html for the relevant link, but when a post is published from mobile I'm not seeing those rel values in the html of the published post.
Needs Verification
The behavior I am observing seems very odd because, in my testing, both mobile and web are saving the same attributes for the block (and even have the same output from the
save
function), but they're resulting in a different output in the published post. This makes me suspicious that there could be an issue with my testing (although I've reproduced this issue multiple times). If someone else has trouble reproducing this issue, then it seems very possible that there may just be something weird going on with my testing setup.The text was updated successfully, but these errors were encountered: