Bug #78513
open
Link-Browser - Link target not changed, if switch between tabs
Added by Ralf Küpper over 7 years ago.
Updated 10 months ago.
Category:
Backend JavaScript
Description
Hallo, all,
in two different installations I found, that the configured link target does not change, if switch between tabs. For example switch from page to url, the link target _self does not change. If switch from page to mail and than back to url, link target changes from _self to _blank as it should. Same with switch from page to file.
Any idea?
Thank you in advance,
Ralf
- Priority changed from Should have to Must have
I performed a test with both 7.6.18 and latest master (9.0.0-dev) using a content element, and clicking on the link icon for the header.
The results are the same for both:
1) I set for example target = new window (_blank) in the "page" tab
2) clicking on other tabs, the target will remain the same, but with one exception :
3) clicking on email tab and then again on another tab, the "target" field got resetted
The behavior I reported on my previous comment is still reproducible on 9.5.1-dev (latest master)
- Related to Bug #83262: Linkhandler popup forgets all settings after switching tabs added
- Related to Feature #87526: LinksController - Override with default on LinkHandler switch added
- Category changed from Backend API to Backend JavaScript
- Status changed from New to Needs Feedback
I fail to reproduce any of the issues in current v9 and v10. Is this issue still relevant?
Either I am doing something wrong or we have a regression here on both 9.5.14 and 10.4.0-dev (latest master):
I am using a content element, and clicking on the link icon for the header_link:
1) I set for example target = new window (_blank) in the "page" tab
2) clicking on other tabs,
Results¶
The target is never kept between the tabs. the same happens for the other configuration attributes, like title or CSS-class or Additional link parameter :/
The results are the same for both 9.5.14 and 10.4.0-dev
My last comment seems still valid for 13.0.0-dev.
What should be the expected behavior?
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by