Live data from Hacker News

Chrome DevTools for Mobile: Screencast and Emulation

html5rocks.com

11–20 of 51 posts

Re: Chrome DevTools for Mobile: Screencast and Emulation

#12
post #8

Earlier quoted context omitted.

Honestly, you're never going to be able to replicate the iPhone without using the browser engine it uses. These Chrome Dev Tools will have nothing to do with iPhone Safari.

Yeah it seems like I'm better off just getting a used 4S.

an iPod touch may be even cheaper.

Re: Chrome DevTools for Mobile: Screencast and Emulation

#13

I'm really in need of accurate iOS Safari emulation in the browser so I hope this brings it. I have a javascript "push-menu" effect that works properly on every device except the iPhone's Safari and debugging it is proving tedious because the effect works in the current dev tols "simulation" of the iPhone as well. On every device the push-menu pushes the other content aside, leaving the button that activated the orig…

check out browserstack.com

Re: Chrome DevTools for Mobile: Screencast and Emulation

#14
post #8

Earlier quoted context omitted.

Honestly, you're never going to be able to replicate the iPhone without using the browser engine it uses. These Chrome Dev Tools will have nothing to do with iPhone Safari.

Yeah it seems like I'm better off just getting a used 4S.

Or get a cheap mac (mac mini, for example). Then you can run the iPhone emulator and use Safari to debug. Works really well.

Edit: Oh, you mean you tried this, but it works differently? Or are you using some linux-based dev tools?

Re: Chrome DevTools for Mobile: Screencast and Emulation

#15
post #14

Earlier quoted context omitted.

Yeah it seems like I'm better off just getting a used 4S.

Or get a cheap mac (mac mini, for example). Then you can run the iPhone emulator and use Safari to debug. Works really well. Edit: Oh, you mean you tried this, but it works differently? Or are you using some linux-based dev tools?

No I've just been using the iPhone user agent "simulation" in Chrome's dev tools. All this does I think it set a reasonably correct resolution and scaling factor, but all the other rendering specifics get overlooked.

Re: Chrome DevTools for Mobile: Screencast and Emulation

#16
post #10

I'm really in need of accurate iOS Safari emulation in the browser so I hope this brings it. I have a javascript "push-menu" effect that works properly on every device except the iPhone's Safari and debugging it is proving tedious because the effect works in the current dev tols "simulation" of the iPhone as well. On every device the push-menu pushes the other content aside, leaving the button that activated the orig…

Note that Chrome for Android (and the desktop emulator) are very different than Safari on iOS. Even when they were both built on top of Webkit, they had different renderers and platform bindings (and the iOS binding was not open source, which caused some of the friction that caused the split). Now that Blink has forked from Webkit, they are diverging even further. So while this means you can do basic mobile web devel…

More details about this here: http://www.paulirish.com/2013/webkit-for-developers/

Re: Chrome DevTools for Mobile: Screencast and Emulation

#17
post #5

Earlier quoted context omitted.

You can remotely debug a Safari session on a device - but it has to be through desktop Safari. It's in the Develop menu.

I'm on Linux and installing a virtual box with a Safari browser just for that seems like too much trouble. I have access to my brother's iPhone but it's annoying for me and for him to have to push my changes to a staging site then go "hey can I use your iPhone for a second" every 5 minutes.

I have had success debugging iOS Safari layout issues with https://github.com/google/ios-webkit-debug-proxy. It claims to support Linux, but I have only used it on a Mac. Could be worth a shot.

Re: Chrome DevTools for Mobile: Screencast and Emulation

#19

I'm really in need of accurate iOS Safari emulation in the browser so I hope this brings it. I have a javascript "push-menu" effect that works properly on every device except the iPhone's Safari and debugging it is proving tedious because the effect works in the current dev tols "simulation" of the iPhone as well. On every device the push-menu pushes the other content aside, leaving the button that activated the orig…

check out browserstack.com

This seems like the holy grail and I will definitely do the free trial to test it out but at this point I am not getting paid for my website development efforts so I'm not ready yet to pay a monthly fee for this (just hacking on something for myself).

Re: Chrome DevTools for Mobile: Screencast and Emulation

#20
post #10

Earlier quoted context omitted.

Note that Chrome for Android (and the desktop emulator) are very different than Safari on iOS. Even when they were both built on top of Webkit, they had different renderers and platform bindings (and the iOS binding was not open source, which caused some of the friction that caused the split). Now that Blink has forked from Webkit, they are diverging even further. So while this means you can do basic mobile web devel…

More details about this here: http://www.paulirish.com/2013/webkit-for-developers/

Right. And this was before the Blink fork; they've diverged even further by now.
Post reply on HN