Closed
Bug 324414
Opened 19 years ago
Closed 19 years ago
caret blinking not themed
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: chpe, Unassigned)
Details
Attachments
(2 files)
2.49 KB,
patch
|
roc
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
2.43 KB,
patch
|
Details | Diff | Splinter Review |
Steps to reproduce:
0) In GNOME control centre's Keyboard applet, uncheck "Blink cursor", or change the cursor blinking time
1) Start a gecko application (firefox, epiphany, etc.)
Result:
Cursor in text fields still blinks, resp. blinks at a different rate than the configured one.
Reporter | ||
Comment 1•19 years ago
|
||
This patch exposes a bug in the caret drawing: when blinking is disabled, the caret doesn't initially show when you click into firefox' URL bar.
Reporter | ||
Comment 2•19 years ago
|
||
The problem with nonshowing cursor with diabled blink might be bug 322720.
Comment on attachment 209352 [details] [diff] [review]
look up cursor blink settings in GtkSettings
+ printf("blink %d blink-time %d\n", blink, blink_time);
lose this.
Attachment #209352 -
Flags: superreview+
Attachment #209352 -
Flags: review+
Reporter | ||
Comment 4•19 years ago
|
||
Sorry about the accidentally left-over debug printf :)
go ahead and check in
Reporter | ||
Comment 6•19 years ago
|
||
(In reply to comment #5)
> go ahead and check in
I can't, don't have cvs write access.
Comment 7•19 years ago
|
||
Chpe, I can check the patch in for you, shall I do this?
Reporter | ||
Comment 8•19 years ago
|
||
(In reply to comment #7)
> Chpe, I can check the patch in for you, shall I do this?
Yes, please :-)
Comment 9•19 years ago
|
||
Checking in widget/src/gtk2/nsLookAndFeel.cpp;
/cvsroot/mozilla/widget/src/gtk2/nsLookAndFeel.cpp,v <-- nsLookAndFeel.cpp
new revision: 1.26; previous revision: 1.25
done
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 10•19 years ago
|
||
this is C++, you don't have to define all your variables at the start of the block. imo you also shouldn't, because it makes it harder to know the type of the variable (where it is used) and makes it harder to see whether it was already initialized.
Reporter | ||
Comment 11•19 years ago
|
||
(In reply to comment #10)
> this is C++, you don't have to define all your variables at the start of the
> block. imo you also shouldn't, because it makes it harder to know the type of
> the variable (where it is used) and makes it harder to see whether it was
> already initialized.
You're right, but I oriented myself on the file's style, which is like this, look e.g. in "case eMetric_SelectTextfieldsOnKeyFocus".
Comment 12•19 years ago
|
||
:( ok, then.
You need to log in
before you can comment on or make changes to this bug.
Description
•