11–20 of 92 posts
WebXR has been great for my app at work, but we're basically locked into the Quest 2 right now because Mozilla dropped the ball on WebXR support. Oculus is the only one doing significant VR work with WebXR in their Oculus Browser, which is a Chromium build that they keep proprietary.
I'm excited to see support for Web Push. I realize that most people associate it with spammy sites asking for permission to send you notifications you don't want, but I think it hasn't really been given a chance because it lacks iOS support. Some things that it enables: - Low-friction asynchronous turn-based games (think “Words with Friends” but you don't have to install an app) - Single-purpose alerts (like CamelCam…
I hate that a regular website I may tap on a search result would ever want to send me notifications. But, if a site that is clearly more of an “application” to me (like an online spreadsheet or chat app, etc) wants to send me notifications, that could be a useful feature.
If there were a more clear delineation between the two, I could just avoid tapping anything that is labeled as an “app” in search results (or just ban them from my search engine), and restrict myself to “plain old webpages” only when searching. And “plain old webpages” would be even further restricted than they already are: No notifications prompts, no ability to see my accelerometer, no offline storage available, etc etc.
It’s nice that the web has turned into a viable app platform, but it doesn’t mean I want every page I visit to be allowed to have “app-like” capabilities. In an ideal world 95% of the web would just be plain old documents accessed over HTTP(S) and the “apps” would be distinguishable as such.
Funny enough, apps were supposed to be just for Apple. The original conception is that 3rd party tools, games, etc. for the iPhone would just be webapps. ( https://9to5mac.com/2011/10/21/jobs-original-vision-for-the-... , etc.) A few adjustments to the model and here we are with lots of native code and big money... but still, folks requesting updates to the the browser to support more app-ish functionality. I'm glad;…
If you have a textarea or input inside a `overflow:scroll` and scroll it out of view or have a `position:fixed` element over it, the text caret or text selection hi-light remains visible outside/above other elements. It's incredibly frustrating for developers of PWA and apps built will frameworks touch as Ionic - it result in text carets and selections being rendered over the top of toolbars and menus.
Effectively the text caret and selection hi-light are drawn above all elements on the page with no detection as to if they should be hidden behind an element or are outside a visible scroll area.
Sounds almost too good to be true, but here is hoping for the best. > Opus audio decoder (enabled) Considering the track record of codec support, I bet it only works when packaged as CAF, singed by QuickTime, and played during the daytime to a limited audience... I joke, but the amount of gotchas I encounter while working with WebAudio API is mindboggling and reminiscent of good ol' days of IE6. Would you guess that…
Off topic, I know, but what in the world does this mean? I did a quick search and couldn't figure it out.
I really can’t see many use cases for web notifications apart from annoying sites trying to bug me. So I’m happy Apple haven’t supported it.
Sounds almost too good to be true, but here is hoping for the best. > Opus audio decoder (enabled) Considering the track record of codec support, I bet it only works when packaged as CAF, singed by QuickTime, and played during the daytime to a limited audience... I joke, but the amount of gotchas I encounter while working with WebAudio API is mindboggling and reminiscent of good ol' days of IE6. Would you guess that…
> in the century of the fruitbat Off topic, I know, but what in the world does this mean? I did a quick search and couldn't figure it out.
Sorry for the confusion, I'm high on caffeine.