Opened 7 years ago
Closed 7 years ago
#17499 closed defect (patchwelcome)
Inconsistent browser behaviour with dijit/Editor and FontChoice plugin
Reported by: | neville1355 | Owned by: | |
---|---|---|---|
Priority: | undecided | Milestone: | tbd |
Component: | Editor | Version: | 1.9.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
This was found by our QA. We currently use a dijit/Editor with the "dijit/_editor/plugins/FontChoice" plugin.
We found that changing the font size after adding a new line seems to cause strange new-line behaviour on the browser.
Use the below fiddle to test: http://jsfiddle.net/x7srk/
Repro steps: 1) Change font size to xx-large 2) type text, e.g. "asdasdasd" 3) Press "enter" to cause a new line 4) Before typing anything, change the font size to xx-small 5) start typing again, e.g. "asdasdasd"
Expected result is that the font and cursor size both change to reflect xx-small as you're typing. However, on different browsers we have different behaviour:
Chome 30:
- Font size is displayed as xx-small but the blinking cursor stays as xx-large causing a large gap between the new line and the previous one
IE9
- Font size and cursor size are both xx-small but there's a large gap between the current line and the previous line
Firefox 28:
- Font size and cursor size are both small but similar large gap as displayed in IE9
- When first pressing "Enter" the cursor cosmetically resets to the start of the first line (see screen shot). This only seems to happen when it's the first line and when no previous text was there.
I've attached screen shots of all the issues described above created in jsfiddle.
Attachments (4)
Change History (6)
Changed 7 years ago by
Attachment: | chrome.png added |
---|
Changed 7 years ago by
Attachment: | firefox enter cursor reset.png added |
---|
firefox cursor resetting to start of string
comment:1 Changed 7 years ago by
Component: | General → Editor |
---|
comment:2 Changed 7 years ago by
Resolution: | → patchwelcome |
---|---|
Status: | new → closed |
Unlikely this will be fixed unless someone wants to supply a patch (including a test case).
chrome 30