Opened 11 years ago

Last modified 8 years ago

#2578 confirmed Bug

Opera browser fit to width loses edit area

Reported by: rockmapper Owned by:
Priority: Low Milestone:
Component: General Version: 3.4.1
Keywords: Opera Discussion Cc: Hallvord R. M. Steen (Opera Software)

Description

When using the Opera browser (V9.52 on Windows XP), if I change the view settings to 'Fit to Width' then the edit area of the FCKEditor disappears. The buttons remain however. This happens within my instance of the editor and also on your demonstration page using V2.6.3 of your editor.

Attachments (1)

krst_19.47.23.png (100.3 KB) - added by Krzysztof Studnik 9 years ago.
Confirmed for Opera 10.61.3484, CKE 3.4.1 Trunk

Download all attachments as: .zip

Change History (7)

comment:1 Changed 11 years ago by Artur Formella

Keywords: Pending WorksForMe added; Opera Fit to width removed

What it mean "Fit to Width"? Do you mean something like:

oFCKeditor.Width = '100%' ;

comment:2 Changed 11 years ago by Alfonso Martínez de Lizarrondo

Keywords: Confirmed Opera added; Pending WorksForMe removed
Milestone: Opera Compatibility
Version: FCKeditor 2.6.3FCKeditor 2.5

That's a feature of Opera. You can find it in the View menu.

Changed 9 years ago by Krzysztof Studnik

Attachment: krst_19.47.23.png added

Confirmed for Opera 10.61.3484, CKE 3.4.1 Trunk

comment:3 Changed 9 years ago by Krzysztof Studnik

Version: FCKeditor 2.53.4.1 (SVN - trunk)

As on attached screenshot, while Fit to width option in Opera is enabled, edit area is set to width equal to width of the toolbars. But editing is still allowed

comment:4 Changed 9 years ago by Tobiasz Cudnik

Keywords: Discussion added

I'm not sure if we should support such features.

comment:5 Changed 9 years ago by Garry Yao

Priority: NormalLow

comment:6 Changed 8 years ago by Hallvord R. M. Steen (Opera Software)

Cc: Hallvord R. M. Steen (Opera Software) added

Feel free to ignore this issue. We should have a look at this at Opera's side to see if the fit-to-width reformatting does something non-optimal (if we find that some of your UI markup makes it very hard to get the algorithm right I could come back with some suggestions of course :-p)

Note: See TracTickets for help on using tickets.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy