I develop on Ubuntu so I can't use ietester. If you need to test things on ie you can download preconfigured VM (for virtualbox) on modern.ie.
As for the side effect you are talking about, it's true that it is sometimes hard to find where does an exception occured because of a requirejs try/catch during pageinit. 2014-11-23 23:54 GMT+01:00 Paul Stanton <pa...@mapshed.com.au>: > I find chrome debugger easier to use and faster than firebug. I used > firebug for years before finding chrome more efficient. > > Once everything works in chrome I take it through firefox+firebug, and > then IE tester for multiple versions of ie (we support 8+). > > I rarely find any issues in safari etc that weren't also issues in either > chrome or firefox. > > One side effect of RequireJS seems to be obscure js exceptions or maybe > i'm still getting used to it. > > p. > > > On 20/11/2014 8:30 AM, Chris Mylonas wrote: > >> No trying yet, I'm pretty sure firebug/devtools would suffice. >> >> My initial request would probably be satisfied with a simple gg search >> "javascript debugging accordion" and getting lucky with a video of someone >> showing their 1337 browser skills - i hadn't imagined remote json debugging >> of dom stuff as readily accessible. >> >> I bought a couple of bootstrap templates to "cut" them up and tapestry54 >> them. Also using tomcat for multiple domains I have put up two t54 test >> sites. >> >> http://www.nursepaging.com/FAQ - an accordion that doesn't work, but as >> a work around just put a table of contents at the top until I figure it out. >> at http://www.businessapps.com.au - clicking on the learn more in the >> slider should make a pop up appear. >> >> The remote debugging seems like overkill....looking at the remote >> debugging protocol though, it seems all the dev tools have been black boxed >> and jsonified - which is really really interesting, particularly >> https://developer.chrome.com/devtools/docs/protocol/1.1/network >> >> Forms with validation from json params is what i'm trying to hammer out >> for the next tapestry sessions, jsr-303 looks the way to go to keep my >> templates & codegen simpler. >> >> All the goodness of having a web layer like tapestry, but I'm just >> carving out simple web sites as an exercise to see where I need further >> study :) I've stayed away from javascript for 10+ years, so it's a bit >> frustrating!!!! >> >> :D >> >> Thanks for the links and phrases to search - I'm seeing way more than I >> bargained for - and this is without even going down the webrtc/websockets >> (although remote debugging is all about websockets) rabbit hole! >> >> Chris >> >> On Wed, 19 Nov 2014 21:10:43 +1100, Charlouze <m...@charlouze.com> wrote: >> >> Have you tried the remote debugging tool also ? >>> >>> 2014-11-18 21:20 GMT+01:00 Chris Mylonas <ch...@opencsta.org>: >>> >>> Thanks charlie >>>> >>>> That mobile testing is quite extreme/thorough looking. I've just been >>>> resizing the browser like a caveman hehe >>>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> . >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
