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
{{ message }}
This repository has been archived by the owner on Feb 7, 2019. It is now read-only.
I have a web application in which I added external links (Information part, where are listed contributors, licence...). Actually, when somebody, tap or click on these links, the external page is load in the same web app, breaking the user navigation. Brick version: 1.0.1 (from stable branch) Step to reproduce:
Create a HTML Element with both attributes completed. Something like: <a href="http://wwwmozilla.org" target="_blank">Go to Mozilla</a>
Load the web page in a browser.
Click on "Go to Mozilla".
What happens:
mozilla.org webpage is loaded in the same page .
What should happen:
mozilla.org is loaded on another page
Workaroud:
A workaround is to add the target="_blank" with javascript only when the concerned x-card is called.
The text was updated successfully, but these errors were encountered:
nicodel
changed the title
[1.0.1] Attribute target disappears from element <a> when page is loaded
[1.0.1] Attribute target disappears from element <a> when page is loaded
Feb 22, 2015
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a web application in which I added external links (Information part, where are listed contributors, licence...). Actually, when somebody, tap or click on these links, the external page is load in the same web app, breaking the user navigation.
Brick version: 1.0.1 (from stable branch)
Step to reproduce:
<a href="http://wwwmozilla.org" target="_blank">Go to Mozilla</a>
What happens:
mozilla.org webpage is loaded in the same page .
What should happen:
mozilla.org is loaded on another page
Workaroud:
A workaround is to add the
target="_blank"
with javascript only when the concerned x-card is called.The text was updated successfully, but these errors were encountered: