Closed
Bug 282017
Opened 20 years ago
Closed 18 years ago
editor loses scrollbar
Categories
(Core :: DOM: Editor, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: surkov, Assigned: mozeditor)
Details
(Keywords: qawanted)
Attachments
(1 file)
|
905 bytes,
application/vnd.mozilla.xul+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 When I open window with editor by openDialog() method with non-empty-string window features then editor shows scrollbar never. Reproducible: Always Steps to Reproduce:
| Reporter | ||
Comment 1•20 years ago
|
||
run it with chrome protocol When you enter too much charackters then scrollbar will apear. Open dialog and enter too much charackters. Scrollbar will not appear.
Updated•20 years ago
|
Summary: editor lose scrollbar → editor loses scrollbar
Comment 2•20 years ago
|
||
Needs a non-chrome testcase using a file:// URI and enablePrivilege.
Keywords: qawanted
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
| Reporter | ||
Comment 4•19 years ago
|
||
confirm Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20050909 SeaMonkey/1.1a
Hi, I have the same problem. I'm using an editor on a dialog window and the scollbars are never visible. If the same editor is used on the "main" browser window, the scollbars works fine.
Confirming ! Wow, this is a bit of a bug, and it makes the <editor> unusable in a dialog.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 8•18 years ago
|
||
Confirming, thunderbird 1.5.0.9, this is a almost two years bug.
Comment 9•18 years ago
|
||
Ok, irc channel give the answer:
You need to include "scrollbars" in the opendialog, sample from irc:
window.openDialog('example.xul', '', 'chrome,modal,centerscreen,resizable,scrollbars');
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 10•18 years ago
|
||
(In reply to comment #9) > Ok, irc channel give the answer: > > You need to include "scrollbars" in the opendialog, sample from irc: > > window.openDialog('example.xul', '', > 'chrome,modal,centerscreen,resizable,scrollbars'); > It looks a tricky a bit or like workaround. I believe xul:editor should be scrollable itself when its content is more than editor's area since xul:editor contains own document and properties of editor's document shouldn't depend on host document. Am I wrong?
| Reporter | ||
Comment 11•18 years ago
|
||
Also, if it confuses not only me then probably Mozilla should be more friendly :)? Or wanted behaviour brokes some mozilla layout paradigms?
| Reporter | ||
Comment 12•18 years ago
|
||
cc'ing Neil to clear questions.
Comment 13•18 years ago
|
||
The scrollbars property is specifically designed to affect the browser or editor with type="content-primary" so you could try type="content" instead.
You need to log in
before you can comment on or make changes to this bug.
Description
•