You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mobile (iOS, Android, webOS, RIM, Windows 7 Mango+, Windows 8 Metro, Nokia N9, etc...)
desktop
legacy
The boilerplate HTML/RequireJS config for loading the correct build for the current environment should be a separate issue.
Should we also provide separate builds for legacy (no IE) and legacy (with old IE support)? The alternative would be to have a single legacy build with the workarounds for all old browsers. Worst case would be delivering extra bytes to old Opera, Firefox and Safari.
The text was updated successfully, but these errors were encountered:
The boilerplate HTML/RequireJS config for loading the correct build for the current environment should be a separate issue.
Should we also provide separate builds for legacy (no IE) and legacy (with old IE support)? The alternative would be to have a single legacy build with the workarounds for all old browsers. Worst case would be delivering extra bytes to old Opera, Firefox and Safari.
The text was updated successfully, but these errors were encountered: