Actions
Bug #7654
closed
Some links cannot be opened in a new tabs
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Medium
Priority:
0
Name check:
Fix check:
Regression:
Description
Those links are of the form javascript:// which effectively disables the open in new tab feature.
They can be found in search results (link to hosts) and in rules parameters (links to groups and to directives).
Updated by Alexis Mousset over 8 years ago
- Has duplicate Bug #8191: We cannot edit a directive in a new tab added
Updated by Benoît PECCATTE about 8 years ago
- Assignee set to Raphael GAUTHIER
- Target version set to 3.1.17
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Raphael GAUTHIER almost 8 years ago
- Status changed from New to In progress
Updated by Jonathan CLARKE almost 8 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Jonathan CLARKE over 7 years ago
- Status changed from In progress to New
Updated by Jonathan CLARKE over 7 years ago
- Assignee deleted (
Raphael GAUTHIER)
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by Raphael GAUTHIER over 7 years ago
The only way is replacing the element containing the onclick event by an <a href=".."> element, but this completly breaks jstree...
Updated by Raphael GAUTHIER over 7 years ago
- Effort required set to Medium
- Priority changed from 29 to 28
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.21 to 3.1.22
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.22 to 3.1.23
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.23 to 3.1.24
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.24 to 3.1.25
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.25 to 387
Updated by Nicolas CHARLES about 7 years ago
- Target version changed from 387 to 4.1.10
this still happens in branch 4.1 and more
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.10 to 4.1.11
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.16 to 4.1.17
Updated by François ARMAND about 6 years ago
- Status changed from New to Rejected
- Priority changed from 28 to 0
I'm closing that one as we can't do anything for it as long as we use jstree (and we removed some cases where it was possible to change the behavior). We will take care to better choose our JS component for the time being.
Actions