what to buy to do minimal iPad safari debugging?
-
Peter_in_2780 wrote:
Like a div initially
visibility:hiddenI'd recommend using the CSS 'display' attribute rather than visibility - it's been around for years and works on all browsers. [CSS display property](https://www.w3schools.com/cssref/pr\_class\_display.asp) If you need to set it in JavaScript, use JQuery's .show() and .hide() methods. Again, works on all browser. The trick is not to try to be clever with this kind of stuff, it's bread and butter stuff that is as easy or difficult as you want to make it (and I've worked on some projects where the devs really want to make it difficult). :laugh:
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
The whole point of using visibility/opacity is that layout is not affected by showing/hiding this particular element. It's either visible or not, nothing nearby moves.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
-
The whole point of using visibility/opacity is that layout is not affected by showing/hiding this particular element. It's either visible or not, nothing nearby moves.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
It's all detailed in these pages: [opacity - CSS | MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/opacity) [visibility - CSS | MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/visibility)
Quote:
Support for visibility: collapse is missing or partially incorrect in some modern browsers. It may not be correctly treated like visibility: hidden on elements other than table rows and columns.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
-
Any suggestions on what mac device to buy so can debug a web page running on iPads. iPhones less worried - if working on iPad will just assume width/height worst problems. all dev work windows with chrome. with iPad being a last test consideration (at the moment). but if page not working, iPad cannot remote debug to windows (currently, maybe some mythical future changes this). Dont want to blow 1k on laptop, if the Mac-minis would be enough. Any comments on using a Mac-Mini for debugging iOS safari? also I guess the OS upgrades a consideration. I know the iPads and MacPros get updates for some time, but do the Mini's, or are people "encouraged" to upgrade to get the latest os? Maybe a second hand would be enough. Not interested in massive dev work. More like, connect it, open safari remote debugger. check line that is the issue. go back to Windows dev machine. fix it. retest. though visual studio code runs on Mac - maybe I just move to a mac, and use the free Microsoft IE vms they provide to test IE.
Any mac will do - though you could blow some coin on a decent one and use parallels or similar to emulate Windows too when you need to- that's my preference as it means I can test on iPad fix code etc. all on the same machine (and build native apps etc. too) - I use VS Code for developing Angular apps mainly - and I'm forced into using a windows machine at work but always prefer my macbook when I can Mac mini will certainly be fine- I'd prob make sure you get one that is at least supported by the current OSX version (late 2009 I believe) MAC OS upgrades are free so are not a concern
PooperPig - Coming Soon
-
Any mac will do - though you could blow some coin on a decent one and use parallels or similar to emulate Windows too when you need to- that's my preference as it means I can test on iPad fix code etc. all on the same machine (and build native apps etc. too) - I use VS Code for developing Angular apps mainly - and I'm forced into using a windows machine at work but always prefer my macbook when I can Mac mini will certainly be fine- I'd prob make sure you get one that is at least supported by the current OSX version (late 2009 I believe) MAC OS upgrades are free so are not a concern
PooperPig - Coming Soon
I'd agree with that - though I would probably say 2011 or newer year to give it a little longevity. My main home machine is a late 2012 Mac Mini that I paid around $600 new and have since upgraded to SSD and 16GB ram and it is more than powerful enough to be a full development machine. One caveat though is that they tend to hold their value - the last time I looked into buying the same model used, they were selling for more than I paid for mine new. That is in part because it was the last model that didn't have the memory soldered in.
-
Any suggestions on what mac device to buy so can debug a web page running on iPads. iPhones less worried - if working on iPad will just assume width/height worst problems. all dev work windows with chrome. with iPad being a last test consideration (at the moment). but if page not working, iPad cannot remote debug to windows (currently, maybe some mythical future changes this). Dont want to blow 1k on laptop, if the Mac-minis would be enough. Any comments on using a Mac-Mini for debugging iOS safari? also I guess the OS upgrades a consideration. I know the iPads and MacPros get updates for some time, but do the Mini's, or are people "encouraged" to upgrade to get the latest os? Maybe a second hand would be enough. Not interested in massive dev work. More like, connect it, open safari remote debugger. check line that is the issue. go back to Windows dev machine. fix it. retest. though visual studio code runs on Mac - maybe I just move to a mac, and use the free Microsoft IE vms they provide to test IE.
Last time i developed for an iDevice i used WeinRe for debugging, it works pretty fine with Chrome.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
Any suggestions on what mac device to buy so can debug a web page running on iPads. iPhones less worried - if working on iPad will just assume width/height worst problems. all dev work windows with chrome. with iPad being a last test consideration (at the moment). but if page not working, iPad cannot remote debug to windows (currently, maybe some mythical future changes this). Dont want to blow 1k on laptop, if the Mac-minis would be enough. Any comments on using a Mac-Mini for debugging iOS safari? also I guess the OS upgrades a consideration. I know the iPads and MacPros get updates for some time, but do the Mini's, or are people "encouraged" to upgrade to get the latest os? Maybe a second hand would be enough. Not interested in massive dev work. More like, connect it, open safari remote debugger. check line that is the issue. go back to Windows dev machine. fix it. retest. though visual studio code runs on Mac - maybe I just move to a mac, and use the free Microsoft IE vms they provide to test IE.
Check out saucelabs.com, able to emulate almost anything and much less expensive than purchasing physical devices.
-
Chances are someone's trying to do something too clever. Any issue like that which I've seen has usually been down to someone developing something that didn't make sense. Not being able to get to a button is a problem caused by the developers not by the device or browser.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
Brent Jenkins wrote:
Chances are someone's trying to do something too clever.
Definitely a possibility. But can one be sure that the OP will not encounter something similar?
Brent Jenkins wrote:
Not being able to get to a button is a problem caused by the developers not by the device or browser.
Yes, but the button was accessible on the desktop. So just testing it on the desktop would not have revealed that. It is possible they tried one simulator years ago (seems like I remember a conversation about that) but it would have been 3-4 years ago so maybe the simulators have gotten better.
-
Brent Jenkins wrote:
Chances are someone's trying to do something too clever.
Definitely a possibility. But can one be sure that the OP will not encounter something similar?
Brent Jenkins wrote:
Not being able to get to a button is a problem caused by the developers not by the device or browser.
Yes, but the button was accessible on the desktop. So just testing it on the desktop would not have revealed that. It is possible they tried one simulator years ago (seems like I remember a conversation about that) but it would have been 3-4 years ago so maybe the simulators have gotten better.
The key thing is either he a) deals with the problems as they occur, fixing them in Chrome on Windows/Linux for free, or b) spends over £1,200 on a MacBook. It's his choice but personally I wouldn't spend that much just on the off-chance that I may need to debug Safari on iOS. It'll spend 99.9% of it's life switched off collecting dust.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
-
It's all detailed in these pages: [opacity - CSS | MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/opacity) [visibility - CSS | MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/visibility)
Quote:
Support for visibility: collapse is missing or partially incorrect in some modern browsers. It may not be correctly treated like visibility: hidden on elements other than table rows and columns.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
Brent Jenkins wrote:
Quote:
Support for visibility: collapse is missing or partially incorrect in some modern browsers. It may not be correctly treated like visibility: hidden on elements other than table rows and columns.
... and
visibility: collapsehas absolutely nothing to do with my point.Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
-
Any suggestions on what mac device to buy so can debug a web page running on iPads. iPhones less worried - if working on iPad will just assume width/height worst problems. all dev work windows with chrome. with iPad being a last test consideration (at the moment). but if page not working, iPad cannot remote debug to windows (currently, maybe some mythical future changes this). Dont want to blow 1k on laptop, if the Mac-minis would be enough. Any comments on using a Mac-Mini for debugging iOS safari? also I guess the OS upgrades a consideration. I know the iPads and MacPros get updates for some time, but do the Mini's, or are people "encouraged" to upgrade to get the latest os? Maybe a second hand would be enough. Not interested in massive dev work. More like, connect it, open safari remote debugger. check line that is the issue. go back to Windows dev machine. fix it. retest. though visual studio code runs on Mac - maybe I just move to a mac, and use the free Microsoft IE vms they provide to test IE.
You don't have to spend $1K, not even close. I faced the same situation awhile back with a web application my organization developed; it worked for every browser, desktop or mobile, except iOS Safari. I picked up a 2009 MacBook Pro running El Capitan with 4GB RAM and 120GB SSD from a local computer shop for $325. With this setup, I was able to connect my iPad and quickly identify the CSS element causing the issue. The deals are out there (local shops, pawn shops, Craigslist, etc.), you just have to be persistent.
-
Brent Jenkins wrote:
Quote:
Support for visibility: collapse is missing or partially incorrect in some modern browsers. It may not be correctly treated like visibility: hidden on elements other than table rows and columns.
... and
visibility: collapsehas absolutely nothing to do with my point.Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
Well you're the one having problems with Safari on iPads, not me. ;P My point is that I'd stay away from visibility altogether and find another way of doing it. The more browsers and devices you want to support, the simpler (and standards compliant) you should keep your code.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.