Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Blink won’t implement pointer events

code.google.com

Post reply on HN
Print view View original

31–40 of 65 posts

Re: Blink won’t implement pointer events

#31

Post by rbyers »

zghst wrote: post #26
fidotron wrote: post #4

People used to complain about mobile device fragmentation, but the web is now looking more fragmented than at any point since IE3 vs Netscape, and whoever else decided to chuck together an excuse for a browser and release it. The approach where all the vendors are ignoring each other as much as possible while pursuing their own improvements has created a giant mess. What is strangling the situation is there is no con…

Pointer events aren't too big of a deal, they are simple polyfills for them. Collaboration between the vendors today has never been better. Just look at IE, it went from being a last place browser to being a second class browser (first class being Firefox and Chrome). IE 10 pioneered CSS grids, the basis for a mature CSS flexbox spec (thank you MS!!!!), CSS regions (although it is only iFrames =/), setImmediate, poin…

Agreed! We had a great "input face-to-face" meeting at Microsoft back in June, and the collaboration between IE, Safari, Firefox and Chrome teams seems better than ever. Despite our differences of opinion, we finally all appear to be working towards common goals with interoperability foremost.

Re: Blink won’t implement pointer events

#32

Post by panzi »

mcav wrote: post #27
zghst wrote: post #23

Seeing that Google doesn't want to add anything to its browser that is not essential and will not penalize performance, this was obviously not going to make the cut. Pointer events would be nice, but using a polyfill isn't so bad. Even if they implemented pointer events, we would still have to implement a polyfill for backwards and cross platform compatibility. For those of who complain of standards, look at the CSS…

(although server-sent-events are supported by just about everything except IE: http://caniuse.com/eventsource )

Given that IE 10+ supports web sockets I don't really see the need for server sent events. What can you do with server sent events that you cannot do with web sockets? I guess one could deprecate SSE in favor of WS.

Re: Blink won’t implement pointer events

#33

Post by panzi »

zghst wrote: post #23

Seeing that Google doesn't want to add anything to its browser that is not essential and will not penalize performance, this was obviously not going to make the cut. Pointer events would be nice, but using a polyfill isn't so bad. Even if they implemented pointer events, we would still have to implement a polyfill for backwards and cross platform compatibility. For those of who complain of standards, look at the CSS…

Shame, I would really like to have cross browser support for CSS Masking and Clipping. Masking stuff with a gradient in particular.

Re: Blink won’t implement pointer events

#34

Post by matthewmacleod »

d7Bw9bPZ wrote: post #25
matthewmacleod wrote: post #3

This is interesting, because I'm pretty sure Microsoft is going to go full steam ahead with pointer events. Indeed, they're the only major vendor of a device that supports both mouse and touch (finger AND stylus) events – it's going to be super important to handle those events well. I'm not totally convinced by the Blink argument – the fact that "touch events are here to stay" is irrelevant, given the unifying nature…

Correct me if I'm wrong, but wouldn't Google themselves be one of those vendors as well? Android has cursor support, and there are a few ChromeOS laptops that ship with touchscreens as well. Although, not owning any of them, I'll readily admit that I'm not sure if/how the browser distinguishes between those events - the OS might be abstracting all of that away too.

Sure, I don't doubt there are other vendors too, and it'll be useful for everybody. Just seems even more so for Microsoft, given their push towards that sort of thing.

Re: Blink won’t implement pointer events

#36

Post by [deleted] »

zghst wrote: post #23

Seeing that Google doesn't want to add anything to its browser that is not essential and will not penalize performance, this was obviously not going to make the cut. Pointer events would be nice, but using a polyfill isn't so bad. Even if they implemented pointer events, we would still have to implement a polyfill for backwards and cross platform compatibility. For those of who complain of standards, look at the CSS…

[deleted]

Re: Blink won’t implement pointer events

#37

Post by chc »

panzi wrote: post #32
mcav wrote: post #27

Earlier quoted context omitted.

(although server-sent-events are supported by just about everything except IE: http://caniuse.com/eventsource )

Given that IE 10+ supports web sockets I don't really see the need for server sent events. What can you do with server sent events that you cannot do with web sockets? I guess one could deprecate SSE in favor of WS.

It's not what you can do, but what you have to do. Websockets are to Server-Sent Events as jet planes are to wheelbarrows. Yes, the stuff jet planes can carry is a superset of the stuff wheelbarrows can carry, but the cost is greater and it ends up being a suboptimal in many cases where you'd want to use a wheelbarrow.

Re: Blink won’t implement pointer events

#38

Post by stephenr »

panzi wrote: post #32
mcav wrote: post #27

Earlier quoted context omitted.

(although server-sent-events are supported by just about everything except IE: http://caniuse.com/eventsource )

Given that IE 10+ supports web sockets I don't really see the need for server sent events. What can you do with server sent events that you cannot do with web sockets? I guess one could deprecate SSE in favor of WS.

SSE is trivial to support via a polyfill, and has none of the connectivity issues websockets has, so it's capable across a much wider array of devices/software both client side and server/network side

I feel that websockets is like the xml of this decade - "everyone is using it" so everyone wants to use it.

Re: Blink won’t implement pointer events

#39

Post by icantthinkofone »

aikah wrote: post #2

If it becomes a standard I guess they will reconsider their choice. We are in a weird era where HTML5/web apis kind of succeeded ,making plugins almost obsolete, yet i'm still not sure 5/10 years from now,vendors will still be on that same line.The temptation of implementing proprietary APIs is still huge. Touch events for instance are a still proprietary API.

It won't become a standard unless there are at least two complete implementations in browsers.
Post reply on HN