> That said, browser-specific permutations has IMO reached a dead-end: > Microsoft will stop support IE<11 in 40 days or so (except IE9 on Vista), > which means that we'll have (hopefully) almost everyone using a "modern > browser" where discrepancies aren't that many and can be dealt with at > runtime without too much overhead.
Why should browser specific permutations ever reach a dead-end? just take a look at any of the items at http://caniuse.com/? whenever a new feature is being introduced, we have the same problems. i.e. WebComponents: in Chrome they work, for Firefox HTML import does not work, for Safari only the Templates work, ... --> this looks like a perfect match for browser specific permutations, doesn't it? -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
