@HenrikJoreteg Oh, I see. If “using†means current mouse position, then you can calculate with the dimensions you get back from the API. Check the photo of my desk setup and look at the sample output in https://t.co/vq2MuVuVyy(…. The iPad is ph
@HenrikJoreteg I was just saying the ID is only defined in the new API. It’s on `ScreenInfo`: https://t.co/5soixtechk.
RT @rowan_m: An overview of Third-Party Origin Trials by @sw12 https://t.co/W7Li18KEbU
As an aside, this comes just in time for Unicode 13…
RT @argyleink: Trying out the @ChromeDevTools Eye Dropper experiment with VisBug in Canary 🤔
The experiment adds a classic “anywhere on t…
@j9t @christianliebel has another remake in the works that has a proper OSS license: https://t.co/8qytnvo5AC. Last time I looked the JSPaint license situation was a little unclear.
RT @addyosmani: 🎉 @ChromeDevTools can now debug CSS Grid *way* better! Try it in Chrome 87 & read the guide https://t.co/QAfkPiPutA by @Jec…
@HenrikJoreteg Check out my demo where I make sure the full screening happens always on the other screen: https://t.co/Gt5g6o4lJn. If you use the API, better to use it exclusively and ignore `window.screen`. The IDs are filled only on the new API. It’s
RT @b1tr0t: Make your PWA feel more like an app https://t.co/l7zQVaRr3e from @tomayac is well worth a read if you haven’t already seen it!