search

manox14 / arora

Automatically exported from code.google.com/p/arora
0 stars 0 forks source link

Textarea paddings are negative and not ajustable #781

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Textareas have text outside their borders. This is a padding issue with (I 
think) a default 
negative padding. Adding a stylesheet for all textareas doesn't solve the 
problem. Inspecting 
the textare show the paddings are set, but nothing happens. A screenshot is 
added to show 
what happens.

Original issue reported on code.google.com by jurian%s...@gtempaccount.com on 10 Nov 2009 at 11:04

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by faw...@gmail.com on 26 Dec 2009 at 6:30

GoogleCodeExporter commented 9 years ago 
I have seen this with some styles, which style are you using?  If you use 
something like plastique do you have the 
issue?

Original comment by ice...@gmail.com on 30 Dec 2009 at 9:07

GoogleCodeExporter commented 9 years ago 
I had the defautl Oxygen style when I noticed the issue. I updated to the beta 
KDE4.4 
lately (Kubuntu Karmic) and it still happens.

Everything is default (style, color, whatever). Because of the update, I know 
it's with Qt4.5 
and Qt4.6.

Original comment by jurian%s...@gtempaccount.com on 30 Dec 2009 at 9:10

GoogleCodeExporter commented 9 years ago 
Sorry for the incomplete answer. I switched to the Plastique style and the 
negative 
margins are gone.

It's still hard to read because there is no margin at all. The textarea borders 
are at the 
same position as e.g. the first vertical line of a letter m, p, b etc. But it's 
better than the 
Oxygen style.

Original comment by jurian%s...@gtempaccount.com on 30 Dec 2009 at 9:14

GoogleCodeExporter commented 9 years ago 
I would send a bug report to the oxygen guys so that they can fix their style 
to behave better.  but yah the usual 
Qt styles should look better too.  hmm I guess opening a bug on bugs.webkit.org 
against the qtwebkit style for 
this would be the best way to have the appropriate QtWebKit developers look 
into it.

Original comment by ice...@gmail.com on 30 Dec 2009 at 9:24

GoogleCodeExporter commented 9 years ago 
Who should be responsible for filing this bug? Is this done yet and if no, 
should I open the 
bug?

Original comment by jurian%s...@gtempaccount.com on 10 Jan 2010 at 8:31