4 ms·

Ahh, we have invented native popups again, about a decade and a half after we managed to successfully block them. In about 3 years we will finally have a popov

Ahh, we have invented native popups again, about a decade and a half after we managed to successfully block them. In about 3 years we will finally have a popover-blocker that eliminates these annoying "subscribe to my newsletter" and "5% off now" popovers. And in 10 years we invent a "slideontop" element, which will have the same functionality.

charcircuit 3y ago
This is not the same thing as a popup window. Clicking on the main window did not close a popup window, but rather backgrounded it. This popup implementation is no different than what is already possible with css.
- pcthrowaway 3y ago
  > This popup implementation is no different than what is already possible with css There are certainly differences. Accessibility, tab functionality, semantics. But most importantly, browsers can sensibly position these to flow away from the edge of the screen when the containing element is at the edge of the viewport (previously with CSS you'd have to choose a direction, and would need Javascript to position anything based on the element's place in the viewport)
jy14898 3y ago
Isn't that a feature? If everyone uses the same API, it makes it easier to block in general
- not_your_vase 3y ago
  Yes, with the current ManifestV2 and ManifestV3 - for now. There is a reason why Google is pushing hard to define what the internet is, and what is possible to do on it and what not. Of course everyone is free to cheer for it. I, for one, refrain from celebrating.
kristiandupont 3y ago
There are popovers everywhere already, so it's not like this is going to introduce them, it will just make it more likely that they close they way you expect them to, handle focus correctly etc. I think it's great. Also, this change will make it easier to make a popover-blocker than it was before.
varenc 3y ago
It doesn't take 3 years. Here you go: *##[popover] That uBlock Origin rule will block any HTML element with a 'popover' attribute. I just tested and can confirm that popovers never display for me now. This is a simple type of ad–block rule that will even work in manifest v3. If blocking popovers is really what you want, you should be celebrating that they're now clearly indicated in the markup. Instead of figuring out the particular incantation to block a popover on some site, you can block them easily per-site or everywhere. If anything, intrusive popover usage will be limited because of how easy they are to block. Ad displayers will end up avoiding them. Of course, I don't think you actually want to do this. There's many uses of popovers that aren't intrusive. But I'm really struggling to see how this makes anything worse.
- that_guy_iain 3y ago
  > Of course, I don't think you actually want to do this. There's many uses of popovers that aren't intrusive. But I'm really struggling to see how this makes anything worse. This is probably the sort of person who disabled JavaScript and went around telling people their site doesn't work without JavaScript instead of enabling JavaScript.
lopis 3y ago
This could replace all the libraries used to create modals, and all their complexity. But I'm afraid people will start blocking all `popover` elements and spoil this for everyone. Anyway, this is Chrome-only for now, so unless Safari implements this, it can't become mainstream.
- supriyo-biswas 3y ago
  Safari has it in its Technology Preview as indicated by the eye icon in the web.dev article.

charcircuit 3y ago

This is not the same thing as a popup window. Clicking on the main window did not close a popup window, but rather backgrounded it. This popup implementation is no different than what is already possible with css.

pcthrowaway 3y ago
> This popup implementation is no different than what is already possible with css There are certainly differences. Accessibility, tab functionality, semantics. But most importantly, browsers can sensibly position these to flow away from the edge of the screen when the containing element is at the edge of the viewport (previously with CSS you'd have to choose a direction, and would need Javascript to position anything based on the element's place in the viewport)

jy14898 3y ago

Isn't that a feature? If everyone uses the same API, it makes it easier to block in general

not_your_vase 3y ago
Yes, with the current ManifestV2 and ManifestV3 - for now. There is a reason why Google is pushing hard to define what the internet is, and what is possible to do on it and what not. Of course everyone is free to cheer for it. I, for one, refrain from celebrating.

kristiandupont 3y ago

There are popovers everywhere already, so it's not like this is going to introduce them, it will just make it more likely that they close they way you expect them to, handle focus correctly etc. I think it's great. Also, this change will make it easier to make a popover-blocker than it was before.

varenc 3y ago

It doesn't take 3 years. Here you go: *##[popover] That uBlock Origin rule will block any HTML element with a 'popover' attribute. I just tested and can confirm that popovers never display for me now. This is a simple type of ad–block rule that will even work in manifest v3. If blocking popovers is really what you want, you should be celebrating that they're now clearly indicated in the markup. Instead of figuring out the particular incantation to block a popover on some site, you can block them easily per-site or everywhere. If anything, intrusive popover usage will be limited because of how easy they are to block. Ad displayers will end up avoiding them. Of course, I don't think you actually want to do this. There's many uses of popovers that aren't intrusive. But I'm really struggling to see how this makes anything worse.

that_guy_iain 3y ago
> Of course, I don't think you actually want to do this. There's many uses of popovers that aren't intrusive. But I'm really struggling to see how this makes anything worse. This is probably the sort of person who disabled JavaScript and went around telling people their site doesn't work without JavaScript instead of enabling JavaScript.

lopis 3y ago

This could replace all the libraries used to create modals, and all their complexity. But I'm afraid people will start blocking all `popover` elements and spoil this for everyone. Anyway, this is Chrome-only for now, so unless Safari implements this, it can't become mainstream.

supriyo-biswas 3y ago
Safari has it in its Technology Preview as indicated by the eye icon in the web.dev article.