#3209 - Allow configuration of "opens in new window" behaviour
| Identifier | #3209 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Allow configuration of "opens in new window" behaviour |
| Status | Open |
| Tags |
Type: Accessibility (custom) Type: Standards compliance (custom) |
| Handling member | Deleted |
| Addon | core_configuration |
| Description | Composr has a standard for when things open in new windows, roughly when a link is not a normal navigation link that is going to open something tangential from what you're currently doing (i.e. where you're very likely want to come back to where you are when you've finished on your tangent).
This is pretty controversial. A lot of people think you should never open new windows, period. We just saw a case of a user on an iPhone not even realise they'd been switched to a new window: https://compo.sr/forum/topicview/browse/deploying/slide-show.htm (which I'm going to resolve as a special case, as those links don't need to open in a new window on a mobile device) Personally I think the current behaviour is logical for moderately-experienced user who understands a desktop environment well. Implementation would be via a Tempcode symbol... <a ... target="{$TARGET_TYPE*,tangential}" title="{$TARGET_TYPE_TOOLTIP*,tangential}...">...</a> We'd have a number of different flags to pass, then the symbol would define whether to make it go in _self or _blank... a) external b) tangential c) external_tangential d) chromeless There'd be config options for each of these flags to specify whether they result in a new window. These options would actually be duplicated - once for desktop, once for mobile. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
There have been no comments yet