> Dão wrote: >> Boris Zbarsky wrote: >>> Martijn wrote: >>>> BBtw, can a script know if ping is enabled/disabled?
>>> At the moment, no.
>> If the browser supports ping, it should say so, but IMO it shouldn't >> expose the enabled/disabled state, as a javascript fallback wouldn't >> be in the user's interest in that case.
> Actually, scripts seem to be able to initiate a POST request [1] and > since you check for your own POST request ;)
Sure, you can always check if a ping got through on the server side. But I think if there's an API as simple as document.implementation.hasFeature("aPing", "1.0"), authors will more likely use that, especially as most users aren't going to disable that feature.
Martijn wrote: > 2007/10/30, Dão <d...@design-noir.de>: >> Boris Zbarsky wrote: >>> Martijn wrote: >>>> BBtw, can a script know if ping is enabled/disabled? >>> At the moment, no. >> If the browser supports ping, it should say so, but IMO it shouldn't >> expose the enabled/disabled state, as a javascript fallback wouldn't be >> in the user's interest in that case.
> Then as a website devver, I would go for the javascript solution, > since that's always working.
If you don't think users should be in control of such things, <a ping> isn't for you in the first place.
> Martijn wrote: > > 2007/10/30, Dão <d...@design-noir.de>: > >> Boris Zbarsky wrote: > >>> Martijn wrote: > >>>> BBtw, can a script know if ping is enabled/disabled? > >>> At the moment, no. > >> If the browser supports ping, it should say so, but IMO it shouldn't > >> expose the enabled/disabled state, as a javascript fallback wouldn't be > >> in the user's interest in that case.
> > Then as a website devver, I would go for the javascript solution, > > since that's always working.
> If you don't think users should be in control of such things, <a ping> > isn't for you in the first place.
Martijn wrote: > 2007/10/30, Dão <d...@design-noir.de>: >> Martijn wrote: >>> 2007/10/30, Dão <d...@design-noir.de>: >>>> Boris Zbarsky wrote: >>>>> Martijn wrote: >>>>>> BBtw, can a script know if ping is enabled/disabled? >>>>> At the moment, no. >>>> If the browser supports ping, it should say so, but IMO it shouldn't >>>> expose the enabled/disabled state, as a javascript fallback wouldn't be >>>> in the user's interest in that case. >>> Then as a website devver, I would go for the javascript solution, >>> since that's always working. >> If you don't think users should be in control of such things, <a ping> >> isn't for you in the first place.
> Exactly.
> Regards, > Martijn
Are you aware that this is an opt-out feature in Mozilla Firefox?
-- Michael Vincent van Rantwijk - MultiZilla Project Team Lead - XUL Boot Camp Staff member (ActiveState Training Partner) - iPhone Application Developer
Gijs Kruitbosch wrote: > Exactly how many people use a "different" OS? How many of them do you > estimate know where about:config is? Because I think the answer to the > first question is "very few" and to the second is "very many". Which was > kind of my point to begin with...
Many people knowing about about:config sound like a UI flaw to me, as they shouldn't even want to know about it if UI is good.
