On Mon, Jan 23, 2012 at 1:40 PM, Lex Berezhny <[email protected]> wrote: > My apologies to Luke for sending him on a wild goose chase.
que? que? > Sevas > ticket said that he was having problems with hulahop not webkit. I > don't know why I said that webkit was missing this. you did? que? que? :) > I would like to respond to both of your comments though. > > I somewhat agree that this should be made to work if it doesn't but > the patch does not actually make this work it simply produces a > situation that silently fails. Silently failing doesn't seem to me > like a good solution. Further more, the "placeholder" is a new HTML5 > feature. If someone is using native placeholders they can't possibly > expect it to work in older browsers. ah if it's an HTML5-only feature then it's not "lowest common denominator", and as such it is entirely the programmer's problem to deal with, *not* pyjamas libraries. > I would either wrap my setPlaceholder in a try/except or check if the > element I'm setting the attribute on supports it. If it does not it > makes sense to do something about it. In your particular code it might > make sense to fail silently but your intentionally making it do that. no i didn't realise it was an HTML5-only feature ... let's double-check that.... http://www.w3.org/TR/html5-diff/ yep it's HTML5-only and, as such, yes it has to be dealt with by the application. i thoroughly agree with your advice, lex. l.
