2 ms·

Yes it's at least partly about Apple and it's partly the fact that Apple doesn't allow browser competition (only skinned Safari). If Apple allowed browser comp

Yes it's at least partly about Apple and it's partly the fact that Apple doesn't allow browser competition (only skinned Safari). If Apple allowed browser competition then Firefox and Chrome would likely support fullscreen mode (like they both do on Android) and Apple would effectively be pushed to add it to mobile Safari or lose market share. On the other hand I wish Google would give me the option to bake in the annotations if they're going to remove them. I have a few instructional videos with corrections in the annotations. Those will be gone and the videos will end up being wrong.

samat 8y ago
Using webkit engine to build a browser is not skinning Safari. There is much more to the browser than rendering engine.
- tokyodude 8y ago
  But as far as what APIs you can expose to JS there is a limit. Can you expose WebGL2? Fullscreen? Screen Orientatio API? WebVR? WebAssembly? Input type=Color, OffscreenCanvas? or do you have to wait for Apple to add them to the base iOS WebKit? Can you fix the fact that iOS Safari shows very poor performance animating while streaming assets?
tinus_hn 8y ago
The web view is just a widget. If you want to make it full screen, make it full screen. Apple is t stopping you.
dhimes 8y ago
OK So I'm trying to understand. This is about using some Google software to annotate videos without actually changing the underlying video? I'm made annotations, but always in my video software (openshot or whatever) so they are baked into the video. They should still work ok. It would be pretty easy to do this for things you really needed. Just import your video and add some keyframes with the overlay. Or maybe you lose your URL when you edit? and just not leave everything up to Google to decide in the future IMHO. EDIT: reading farther down, I see the answer to the latter half: https://news.ycombinator.com/item?id=18540470 https://news.ycombinator.com/item?id=18540470
- tokyodude 8y ago
  That is one solution. For me the issue is time. Adding the annotation took 1-2 mins. Downloading the video on youtube (since I no longer have the source material), then loading that into some video editor, adding the annotations, rendering it, and re-uploading it would easily take 1hr per video. So IMO it's not really a good solution. I don't have the time. Personally I think they should keep the annotations and keep the source video. When you change the annotations they can re-render the video on their end. Keep the 1-2 minute workflow

samat 8y ago

Using webkit engine to build a browser is not skinning Safari. There is much more to the browser than rendering engine.

tokyodude 8y ago
But as far as what APIs you can expose to JS there is a limit. Can you expose WebGL2? Fullscreen? Screen Orientatio API? WebVR? WebAssembly? Input type=Color, OffscreenCanvas? or do you have to wait for Apple to add them to the base iOS WebKit? Can you fix the fact that iOS Safari shows very poor performance animating while streaming assets?

tinus_hn 8y ago

The web view is just a widget. If you want to make it full screen, make it full screen. Apple is t stopping you.

dhimes 8y ago

OK So I'm trying to understand. This is about using some Google software to annotate videos without actually changing the underlying video? I'm made annotations, but always in my video software (openshot or whatever) so they are baked into the video. They should still work ok. It would be pretty easy to do this for things you really needed. Just import your video and add some keyframes with the overlay. Or maybe you lose your URL when you edit? and just not leave everything up to Google to decide in the future IMHO. EDIT: reading farther down, I see the answer to the latter half: https://news.ycombinator.com/item?id=18540470 https://news.ycombinator.com/item?id=18540470

tokyodude 8y ago
That is one solution. For me the issue is time. Adding the annotation took 1-2 mins. Downloading the video on youtube (since I no longer have the source material), then loading that into some video editor, adding the annotations, rendering it, and re-uploading it would easily take 1hr per video. So IMO it's not really a good solution. I don't have the time. Personally I think they should keep the annotations and keep the source video. When you change the annotations they can re-render the video on their end. Keep the 1-2 minute workflow