go-button on quicksearch?
-
stm999999999
- Regular
- Posts: 1531
- Joined: Tue Mar 07, 2006 11:25 pm
- Location: Berlin, Germany
- Contact:
go-button on quicksearch?
After updating my installations I get a ">" / "go!"-Button behind my search field - is there any way to delete this?
Ciao, Stephan
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: go-button on quicksearch?
Hi!
Hm, at least not with CSS 2
I just updated SVN and gave that go-button a class name with which you can specifically address it with CSS.
The button was added because of accessibility reasons.
Regards,
Garvin
Hm, at least not with CSS 2
I just updated SVN and gave that go-button a class name with which you can specifically address it with CSS.
The button was added because of accessibility reasons.
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
-
Don Chambers
- Regular
- Posts: 3657
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
Re: go-button on quicksearch?
Is this addition just for 1.3? I don't see it updated in 1.2 branch.....garvinhicking wrote:Hi!
The button was added because of accessibility reasons.
Regards,
Garvin
What is the issue with accessibility? If this is an issue, it would be nice to see in 1.2 so we can address the same thing for bp.
=Don=
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: go-button on quicksearch?
Hi!
Yeah,thisis 1.3 only.
regards,
Garvin
Yeah,thisis 1.3 only.
I didn't backport it to 1.3 because of the BC-impactit has. IMHO it's not worth backporting to 1.2...What is the issue with accessibility? If this is an issue, it would be nice to see in 1.2 so we can address the same thing for bp.
regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
-
stm999999999
- Regular
- Posts: 1531
- Joined: Tue Mar 07, 2006 11:25 pm
- Location: Berlin, Germany
- Contact:
Re: go-button on quicksearch?
something like display: none, right?garvinhicking wrote: I just updated SVN and gave that go-button a class name with which you can specifically address it with CSS.
Ciao, Stephan
-
Don Chambers
- Regular
- Posts: 3657
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
Re: go-button on quicksearch?
Seems right to me!stm999999999 wrote:something like display: none, right?
@ Garvin - what is the specific accessibility issue to using a button, and why is this such a problem to backport to 1.2? I really do not want to start a 1.3bp branch right now... but since we do have an option to display a quicksearch field in the bp navbar, I think we need to give this some thought.
=Don=
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: go-button on quicksearch?
Hi!
I dislike the backporting because somewhere we have to draw a line between 1.2 and 1.3, backporting is always hard because it increases the overhead for maintaining...
Regards,
Garvin
It's simply that HTML forms without a submit button are thought to be not accessible, because a screenreader cannot "push" an input text button.@ Garvin - what is the specific accessibility issue to using a button, and why is this such a problem to backport to 1.2? I really do not want to start a 1.3bp branch right now... but since we do have an option to display a quicksearch field in the bp navbar, I think we need to give this some thought.
I dislike the backporting because somewhere we have to draw a line between 1.2 and 1.3, backporting is always hard because it increases the overhead for maintaining...
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/