#16024 closed defect (fixed)
Editor's AlwaysShowToolbar plugin on of cuts off bottom text on resize
Reported by: | Matt Lauer | Owned by: | haysmark |
---|---|---|---|
Priority: | undecided | Milestone: | 1.9 |
Component: | Editor | Version: | 1.6.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
When using a dijit.Editor with the dijit._editor.plugins.AlwaysShowToolbar? plugin and the Toolbar becomes fixed to the top of the viewport and the Editor resizes (most commonly from just hitting enter) it cuts off the last line text/markup in the editor due to the height of the Toolbar being applied to the Editor's iframe as margin-top. I use v1.6.1 of the toolkit and it has the same problem as the nightly tests.
Demo: http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/editor/test_Editor.html
- Go to the "Created from div, auto-expanding" test
- Scroll down enough so the Toolbar is fixed to top of your viewport and you can still see some of the Editor
- Put your cursor after "Sed vitae risus." and hit Enter
- Watch the next line " The following HTML should appear as source: <INPUT TYPE="IMAGE" SRC="javascript:alert('no scripting attacks')"> " disappear.
- You can scroll up (so the Toolbar returns to normal spot) and delete that new paragraph and watch the line appear again.
The iframe (in dijitEditorIFrameContainer) gets a margin-top applied everytime the Toolbar fixes to the top of the viewport. The Iframe has the right calculated height, but the margin/toolbar height somehow compounds to hide the last N pixels of the Editor. If you remove the iframe's margin-top setting manually and hit enter again (to trigger the resize) the bottom line will reappear.
This issue seems to affect all browsers (IE, Chrome, FF on Win 7 that I tried).
Somewhat related issue with AlwaysShowToolbar? plugin: when the cursor is on the last line of the Editor in Firefox and the user hits the down arrow key the cursor jumps all the way to the top of the Editor. This is usually out of sight on long pages and a undesired behavior. This only happens in Firefox.
Change History (4)
comment:1 Changed 10 years ago by
comment:2 Changed 9 years ago by
Owner: | set to haysmark |
---|---|
Status: | new → assigned |
comment:4 Changed 9 years ago by
Milestone: | tbd → 1.9 |
---|
Is anyone going to be assigned this bug? It's a somewhat significant yet minor issue.