The spec of flex layout requires it to layout its child elements several times to compute actual layout. Make it deep and nested without proper constrains will results in n*n*n*n… layout computations and bring down the browser on resize.
Deleted Comment
The spec of flex layout requires it to layout its child elements several times to compute actual layout. Make it deep and nested without proper constrains will results in n*n*n*n… layout computations and bring down the browser on resize.
Considering the kinds of crap that have been done with headers...
Am I just an old man?
Edited: It seems it can also be toggled from css variable? So it might actually fix some existing problems.
So if you wanted to use a different browser or install a PWA without a connection to the internet, or without Google Play, all you get is a bookmark.
In my personal experience, it only validate whether manifest is malformatted though. Although it's still up to google if they want to do something wonky.
Unfortunately both Google and Apple very early on identified that it was in their best interest to keep the concept around in a half-dead state and ensure nobody really built on it...
You get notification. You can autoplay video/audio. You get whaterver video or element full screen with all necessary UI. You get rotation lock. You have a fullscreen to do what ever you want for any purpose. You probably can't touch hardware APIs(for example: bluetooth/nfc) like native app. But that isn't really needed for most apps either.
On the other side. Apple seems sabotage the PWA as much as possible. You can't autoplay video/audio. You can't even fullscreen anything other than video, and when fullscreen video, UI is ignored. Also there is no way to disable gesture so your app will misfire system gesture. And you can't lock the rotation either. There is no way to auto rotate the video player or whatever when maximized either.
It's really a golden example for pretend to do something while actually not. It seems you can do pretty much everything with ios pwa. And when you try to do it. You will figured out it will have a worse experience than native app because all sort of issues.
Every time I've tried it in the last 10 years, it's felt like I was teleported into the late 90s PC era - weird bugs in specific drivers that you can find lots of reports of for this specific model and no resolution, heat management that feels like someone in a basement strung things together in 5 minutes and never tested it again, strange failures in "plug and play" support for USB devices that work on every other machine flawlessly with the same cable and device, and don't get me started on Bluetooth. (My favorite ever might be the time that attempting to pair a specific pair of headphones to the laptop shut off every USB port, reproducibly, apparently because the BT adapter was connected over the USB M.2 pins to the root hub, and was crashing in firmware, so both Windows and Linux did the same style of dance of "try to reset it, once that fails, go up a level and turn off the complex to make sure other things keep working"...except up one level was the root.) (Though, to be fair to AMD, that was an Intel BT/wifi chip in an AMD laptop...)
I really want to like and recommend AMD mobile hardware, but every time I've tried it has been a shitshow without fail.
Also, the game does give you a hint about how to bruteforce the level if you only have one square left. Good job.
I came across some more technical information here: https://doublepulsar.com/small-numbers-of-notepad-users-repo...