New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the "placeholder" attribute on the "input" tag #84
Comments
@nixta i was not able to tag you as a reviewer, can you test my branch and see if I addressed this? the UI is a bit different now but it seems to be something more intuitive. |
Yeah, works much better. Nice work. I think we should fix up the CSS before we release though. Seems the CSS from the old chosen library was just copied wholesale into our home.css and there isn't a proper match now. Should mostly be some overrides for the bubble sizes and backgrounds, and the chooser line height. @alaframboise might have some insight here, but it was so long ago I wouldn't be surprised if that information has been flushed. Cheers, Nick. |
Hmmm. I must be a foreigner in this repo. I can't assign myself, but I'll take a stab at updating the CSS. |
not anymore. you've earned the 🔑s |
PR #99 submitted. |
There are a few nasty UI conflicts because the greyed out "Search by topic..."
placeholder
behavior is implemented by controlling the input field'svalue
attribute.To reproduce:
runtime
).runtime
).2 issues seen. In both the following screenshots, I typed
runtime
again once the topic bubble had been dismissed.Search by topic...ru
before the text was cleared, leaving only thentime
ofruntime
.The
input
tag used for search should be showingSearch by topic...
as aplaceholder
attribute, not thevalue
attribute.The text was updated successfully, but these errors were encountered: