Actions
Bug #11990
closed
Broken text/js button in directive form in chrome
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
45
Name check:
Fix check:
Regression:
Description
See attached screenshot, on Firefox 57.
Files
Updated by Benoît PECCATTE almost 7 years ago
- Severity set to Trivial - no functional impact | cosmetic
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Priority changed from 0 to 47
Updated by Vincent MEMBRÉ almost 7 years ago
It's ok to me in firefox in all version (4.1/4.2/4.3)
but in chrome it's not ok ... in all version (4.1/4.2/4.3)
Updated by Vincent MEMBRÉ almost 7 years ago
- Subject changed from Broken text/js button in directive form to Broken text/js button in directive form in chrome
- Target version changed from 4.3.0~beta1 to 4.1.10
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
- Priority changed from 47 to 45
Updated by Alexis Mousset over 6 years ago
- Is duplicate of Bug #12514: CSS of txt/json inputs is broken added
Actions