Bug 38400 - [wish-list] Font colour bucketfill not being initiated from clicking on a palette colour (unlike highlight does)
Summary: [wish-list] Font colour bucketfill not being initiated from clicking on a pal...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.3.3 release
Hardware: x86-64 (AMD64) Linux (All)
: low enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-17 04:29 UTC by johnoradcliffe
Modified: 2012-08-31 10:06 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description johnoradcliffe 2011-06-17 04:29:22 UTC
Where switching continuously between writing and varying colouration, having to use the toolbar button to initiate the font colour bucketfill slows progress for no apparent benefit. Highlight bucketfill has this option.
Font bucketfill would be better with it too IMHO.
Comment 1 Akira TAGOH 2011-09-05 18:50:52 UTC
How is this related to fontconfig? that looks like an RFE for applications or the rendering library somehow.
Comment 2 johnoradcliffe 2011-09-10 05:50:12 UTC
It probably is not, a product had to be chosen to file the request, so fontconfig was my best guess.
Any corrections appreciated. In future in these comments i can state the product choice was a guess.
Comment 3 Akira TAGOH 2011-10-05 21:46:47 UTC
I guess you better ask someone who is maintaining the application that you want to have that feature on.
Comment 4 johnoradcliffe 2011-10-30 04:26:15 UTC
Will do Akira,thanks for your time. The product component is a guess.
Comment 5 Björn Michaelsen 2011-12-23 12:27:24 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 6 Florian Reisinger 2012-08-14 14:02:42 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 Florian Reisinger 2012-08-14 14:03:38 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 8 Florian Reisinger 2012-08-14 14:08:13 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 9 Florian Reisinger 2012-08-14 14:10:18 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian