7 ms·

Linux/Firefox: Paddle doesn't move and the paddle popup doesn't bounce the ball. Linux/Chrome: Paddle doesn't move but the paddle popup does bounce the ball.

Retr0id 3y ago
Same Linux/Firefox experience here, and I'm on Wayland, which I have a feeling might be relevant. Edit: also GNOME 45
- remedan 3y ago
  To add another data point, it works for on me on Linux/Firefox/X. So the Wayland theory might be correct.
  - prmoustache 3y ago
    Which makes me glad I am using wayland. I am not comfortable with the idea that one browser window could be aware of things like the position of another browser window on my desktop.
    - alt227 3y ago
      Are you really that worried that firefox is aware of the desktop coordinates of 2 of its own windows?
      - berkes 3y ago
        Better even: the parent window knows the position of it's child window. So firefox only knows the one window. And that in a situation where you actively had to allow the permission for the parent to spawn the child in the first place. Sounds nothing but reasonable to me.
      - dahart 3y ago
        Firefox knows where all its windows are, of course, but that’s not the potential issue being raised. The problem is allowing untrusted javascript access to that info. Luckily, Firefox doesn’t do that, it only allows you (JavaScript author) window information for the windows you’ve directly opened in code.
        bandrami 3y ago
        Not on Wayland it doesn't. Nor does it know if either window is visible, nor if it has been damaged since the last render.
        boudin 3y ago
        Actually I don't think Firefox knows the position of the window in Wayland. I thought that coordinates of windows were considered as a compositor concern and not shared with the client.
    - dahart 3y ago
      The browser doesn’t communicate such things between unrelated clients, say, on different domains. The browser does allow a site to communicate with the popup that it opened, which is what this game is doing, and is not problematic.
      - sdeframond 3y ago
        Are you aware of the window.screenX property? It does not really seem to have any restriction. Does it? https://developer.mozilla.org/en-US/docs/Web/API/Window/screenX https://developer.mozilla.org/en-US/docs/Web/API/Window/scre...
        dahart 3y ago
        Yes, you can access window.screenX for your own window, but not for other windows. If you’re writing code for an iframe embedded into a domain that’s not yours, your code does not have access to the parent’s windows.screenX.
  - mnd999 3y ago
    Same with sway. It also tiles the windows for you, which doesn't help.
- Prunkton 3y ago
  works fine for me on: KDE 5.27.9 Qt 5.15.11 Wayland 1.22.0-1 Firefox 120.0 upper bound of the inner window is not perfect though
  - humanfromearth9 3y ago
    so you have KDE on top of Qt on top of Wayland on top of Firefox -> are you running wayland in Firefox? if yes, you might run Firefox in Wayland instead of xorg to have some further *ception
focusedone 3y ago
Linux/Firefox: Works fine here. KDE Neon 5.27 Only issue is the low resolution screen on my old Thinkpad makes it difficult to see the entire game area. Super cool game! Plays great on higher res screens, just wanted to test on Linux.
_lnrx 3y ago
Game is working fine for me. Linux/Chrome on gnome with enabled wayland ozone.
Jnr 3y ago
Linux/Wayland/Firefox: it doesn't interact with the window since wayland probably doesn't provide location data. Linux/Wayland/Chromium: chromium crashes as soon as I click "launch game" :))
Self-Perfection 3y ago
Linux/Xorg/Firefox/KDE Paddle coordinate gets updated only when I release the paddle window.

Retr0id 3y ago

Same Linux/Firefox experience here, and I'm on Wayland, which I have a feeling might be relevant. Edit: also GNOME 45

remedan 3y ago
To add another data point, it works for on me on Linux/Firefox/X. So the Wayland theory might be correct.
- prmoustache 3y ago
  Which makes me glad I am using wayland. I am not comfortable with the idea that one browser window could be aware of things like the position of another browser window on my desktop.
  - alt227 3y ago
    Are you really that worried that firefox is aware of the desktop coordinates of 2 of its own windows?
    - berkes 3y ago
      Better even: the parent window knows the position of it's child window. So firefox only knows the one window. And that in a situation where you actively had to allow the permission for the parent to spawn the child in the first place. Sounds nothing but reasonable to me.
    - dahart 3y ago
      Firefox knows where all its windows are, of course, but that’s not the potential issue being raised. The problem is allowing untrusted javascript access to that info. Luckily, Firefox doesn’t do that, it only allows you (JavaScript author) window information for the windows you’ve directly opened in code.
      - bandrami 3y ago
        Not on Wayland it doesn't. Nor does it know if either window is visible, nor if it has been damaged since the last render.
      - boudin 3y ago
        Actually I don't think Firefox knows the position of the window in Wayland. I thought that coordinates of windows were considered as a compositor concern and not shared with the client.
  - dahart 3y ago
    The browser doesn’t communicate such things between unrelated clients, say, on different domains. The browser does allow a site to communicate with the popup that it opened, which is what this game is doing, and is not problematic.
    - sdeframond 3y ago
      Are you aware of the window.screenX property? It does not really seem to have any restriction. Does it? https://developer.mozilla.org/en-US/docs/Web/API/Window/screenX https://developer.mozilla.org/en-US/docs/Web/API/Window/scre...
      - dahart 3y ago
        Yes, you can access window.screenX for your own window, but not for other windows. If you’re writing code for an iframe embedded into a domain that’s not yours, your code does not have access to the parent’s windows.screenX.
- mnd999 3y ago
  Same with sway. It also tiles the windows for you, which doesn't help.
Prunkton 3y ago
works fine for me on: KDE 5.27.9 Qt 5.15.11 Wayland 1.22.0-1 Firefox 120.0 upper bound of the inner window is not perfect though
- humanfromearth9 3y ago
  so you have KDE on top of Qt on top of Wayland on top of Firefox -> are you running wayland in Firefox? if yes, you might run Firefox in Wayland instead of xorg to have some further *ception

focusedone 3y ago

Linux/Firefox: Works fine here. KDE Neon 5.27 Only issue is the low resolution screen on my old Thinkpad makes it difficult to see the entire game area. Super cool game! Plays great on higher res screens, just wanted to test on Linux.

_lnrx 3y ago

Game is working fine for me. Linux/Chrome on gnome with enabled wayland ozone.

Jnr 3y ago

Linux/Wayland/Firefox: it doesn't interact with the window since wayland probably doesn't provide location data. Linux/Wayland/Chromium: chromium crashes as soon as I click "launch game" :))

Self-Perfection 3y ago

Linux/Xorg/Firefox/KDE Paddle coordinate gets updated only when I release the paddle window.