Closed GoogleCodeExporter closed 9 years ago
BTW same behavior in IE7.
Original comment by runef...@gmail.com
on 30 Nov 2012 at 12:54
This is the intended behavior of the plugin.
Original comment by t...@speednet.biz
on 30 Nov 2012 at 1:06
Ok - But in Firefox (on Mac), the watermark stays when the field gets focus?
Original comment by runef...@gmail.com
on 30 Nov 2012 at 1:11
That's because it is using the browser's native watermark (placeholder)
capabilities. Read the documentation here.
Original comment by t...@speednet.biz
on 30 Nov 2012 at 2:04
Thanks - Yes I did read the documentation. I did run non native with the
result, that the watermark disappeared when the field got focus.
Anyway - I didn't know that this was the intented behavior in the first place.
Are there any way to customize the plugin so that watermark only disappears
when the user starts typing (like native Firefox behavior)?
Original comment by runef...@gmail.com
on 30 Nov 2012 at 2:10
You would have to use some other plug-in that works that way. This is pretty
complex stuff to get right, so you would have to find a plugin that was
designed completely differently. In my opinion, users of older browsers are
familiar with the disappearing watermarks, and they become confused when it
does not disappear upon focusing the element. But to each their own.
Original comment by t...@speednet.biz
on 30 Nov 2012 at 2:30
Ok - What a shame. It seems like a good plugin.
BTW isn't it quite standard behavior that the search field on a page (Google
f.ex.) gets the focus right when the page loads? In that case the user will
never see the watermark using this plugin.
Original comment by runef...@gmail.com
on 30 Nov 2012 at 2:37
It *is* a good plugin. Your personal opinion on how it should work does not
change that. There is no "shame". I hope you find what you're looking for.
Original comment by t...@speednet.biz
on 30 Nov 2012 at 2:54
[deleted comment]
Just a comment for others. This is easily obtained by changing the ".focus"
event check to the event ".keydown". Haven't discovered any side effects yet.
Original comment by runef...@gmail.com
on 5 Dec 2012 at 1:44
Original issue reported on code.google.com by
runef...@gmail.com
on 30 Nov 2012 at 12:48