Timeline for How should I structure my web app for browser compatibility?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2015 at 22:09 | audit | Suggested edits | |||
| Aug 7, 2015 at 22:10 | |||||
| Jul 22, 2015 at 16:54 | answer | added | greyfade | timeline score: 1 | |
| Jul 22, 2015 at 15:52 | comment | added | bbsimonbb | You're right, we are incredibly reluctant to bring in dependencies of any kind. I've the feeling there are others we miss more cruelly than jquery, but it's not a fight I'm going to win today. Could you please focus on the folder structure aspect, which is independent of jqery and browser compatibility? | |
| Jul 22, 2015 at 15:42 | comment | added | gbjbaanb | Fnd out why they dropped jQuery becuase often its "because we didn't make it" (which will be couched in terms of 'not being good enough' or similar). Sometimes its simply because they didn't spend enough time learning it because they didn't want to, because NIH. Any issues with jQuery can be fixed.. and submitted to the jQuery team. | |
| Jul 22, 2015 at 15:38 | comment | added | bbsimonbb | Our team has tried, then dropped, jquery, after version changes broke some stuff. My proposed folder layout keeps most of the same advantages, whether or not you need browser-specific overrides. And I've the impression there's always something. IE11 doesn't support the HTML5 date input, so if you want to use it where it's available, and cover for it when it isn't, straight away you need IE specific markup and scripts. | |
| Jul 22, 2015 at 15:29 | comment | added | Basile Starynkevitch | Can't you use toolkits like Jquery claiming to deal with browser compatibility? | |
| Jul 22, 2015 at 15:24 | history | asked | bbsimonbb | CC BY-SA 3.0 |