Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It is unclear what the compatibility is of these samples #24

Open
0xR opened this issue May 28, 2016 · 5 comments
Open

It is unclear what the compatibility is of these samples #24

0xR opened this issue May 28, 2016 · 5 comments

Comments

@0xR
Copy link

0xR commented May 28, 2016

I am considering of using the techniques shown in these samples, but in order to do so in production I have certain compatibility requirements.

I just tried the samples in IE9 and nothing works.

It would help if the README would show in which browsers these examples would work and whether it is possible to use the techniques shown in older browsers with some tweaking.

@0xR
Copy link
Author

0xR commented May 28, 2016

Ps: I did run the babel transpilation, but that doesn't help much.

@DanielVoogsgerd
Copy link
Contributor

DanielVoogsgerd commented May 29, 2016

IE11 does not support ES6 classes, so without transpiliing you might have to move to edge anyway if you want native support.
The reason it doesn't work on IE9 with transpiling is (partially) because IE9 needs the ms prefix for transform.

I would be very cautious with moving these samples to production. The code is written with BEM in mind. BEM is awesome for prototyping, but might not be really what you might want in your production code.

I think that the motivation behind these elements is more to demonstrate techniques and features supported by the next generation web, than it is to craft production-ready "elements".
If you want those you might want to take a look at the polymer elements.

@DanielVoogsgerd
Copy link
Contributor

Also TouchEvents are not supported by edge.

@paullewis
Copy link
Contributor

Right exactly what @DanielVoogsgerd said. The code is here for reference because they are live-coded, but I will definitely add a note to the README so that it's setting expectations more clearly.

@github-polymer-user
Copy link

@DanielVoogsgerd @0xR @paullewis @dglazkov @sethladd

For anyone willing to debug on their own lovly OS X and Safari, just add some browser polyfills:

  1. npm install bower && bower install webcompnentsjs (instuctions from http://webcomponents.org/)
  2. add <script src=""/browser/webcomponents-lite.min.js"></script> to the header section of the header.partial.html file
  3. add app use section app.use('/browser',express.static('./app/../bower_components/webcomponentsjs'));
  4. add extra -moz-, -webkit-, -o-webkit- CSS animation and/or html5shim.js as needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants