Issue 51247

Summary: HSB colour dialog allows unreasonable entries
Product: Impress Reporter: stefan_koehler <koehler.stefan>
Component: uiAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P4 CC: issues
Version: 680m110   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description stefan_koehler 2005-06-27 09:49:27 UTC
In the edit colour dialog the field for hue allows entries beyond the reasonable
range between 0-359 (i.e. 521). Result is set to maximum (359) when shifting
mouse focus, though.
Comment 1 christian.guenther 2005-06-28 18:33:06 UTC
one for me (cgu)
Comment 2 christian.guenther 2005-06-28 18:35:33 UTC
This is not a bug.
The HSB color schema has the values for 

Hue           -> 360
Saturation  -> 100
Brightness -> 100

Please have a look on this page
Comment 3 christian.guenther 2005-06-28 18:36:01 UTC
I close the issue as invalid.
Comment 4 stefan_koehler 2005-06-28 20:19:33 UTC
That is not the point, the HSB schema is correctly implemented. The point is,
should users be allowed to type in values beyond the valid range without getting
a notification or without letting the software correct the input to the highest
possible value (359). I find it confusing to be able to choose 800 as a value
and get away with it.


Comment 5 stefan_koehler 2005-06-29 12:38:24 UTC
Ok, since all dialogs in the colour options allow strange entries like 15000 in
CMYK (and autocorrect themselves when loosing focus), I do not insist on the HSB

So close this issue, thanks.

Comment 6 christian.guenther 2005-06-29 14:51:20 UTC
We should not be able to insert valuse which are higher then the max value of
the field.
This is an enhancement of all fields where I can insert a value not only with
the HSB  color dialog.
Comment 7 ace_dent 2008-05-16 00:22:51 UTC Issue Tracker - Feedback Request.

The Issue you raised is currently assigned to 'Requirements' pending review, but
has not been updated within the last 3 years. Please consider re-testing with
one of the latest versions of OOo, as the problem(s) may have already been
addressed. Either use the recent stable version:
or consider trying the new OOo 3 BETA (still in testing):
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
Many thanks,
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~