-
Notifications
You must be signed in to change notification settings - Fork 155
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
vaadin-grid Polymer 2.0 support #710
Comments
Things to consider:
|
Also, we can most likely have only one shadow root between the cell containers in |
Regarding the proposal of refactoring fixed elements to their own containers (which is currently struck out), to which I commented that it prevents the use of We should evaluate the tradeoffs here. Is it more beneficial to have the scrolling more smooth, at the expense of making it more difficult to add hover styles? I mean, we could move the fixed elements to their own containers and then add mouse event listeners for the row elements that toggles a So, how big of a performance and styling convenience penalty would we get from toggling the ´[hovered]` attribute on each row (it should probably be prevented during scrolling anyways) vs. the performance penalty we get from supporting fixed elements inside the scrolling container? |
Added one more thing to consider during this refactoring: deprecate CSS mixins. This should apply to all of our hybrid elements (the next minor versions). Edit: in case someone is wondering why, the reason is that since the future support for CSS mixins is currently under consideration by the W3C working group, we don’t want to depend on it. Also, as a mechanism for comprehensive styling support, they are not really that ideal. See this issue for more discussion and details. |
We do see a lot of errors under Polymer 2.0 with 2.1-polymer-2 branch, so my question is when vaadin-grid will be available for alpha testing . |
@lchen2017 as soon as we can. Unfortunately, it turned out to be challenging to port such a complex element, but we are actively working on it these days. Please keep watching this issue to track the progress. |
@platosha Thanks! are there any tasks we can help with? |
A small update for those interested: the Current situation: all tests are currently passing on Chrome + Polymer If you try the dev branch out and find problems, please don't file new issues at this point yet, but instead add a comment here or contact us in the Gitter chat room. Thanks! Update: Safari and Firefox pass tests now also on Polymer 2. |
Curious - what does moving this from in-progress to backlog mean, for those of us hoping to use vaadin-grid under Polymer 2.x? =) |
Hi @victorhooi! We had to change priorities for a week or two to work on other things, but rest assured, we'll pick it back up shortly. |
@Saulis I'm having trouble in getting all dependencies right with bower install. Its complaining about "ECONFLICT Unable to find suitable version for webcomponentsjs". (using Polymer-cli@next) Can you give a hint on how to get it right? |
@andersforsell hmm strange.. which exact version of Polymer CLI are you running? Mine reports Tried clearing out my bower cache and everything and everything seems to install smoothly. |
I'm also seeing weirdness/issues around package versions. I'm running Polymer CLI
I create a new Polymer 2.0 project:
I then try to install vaadin-grid:
Is the above expected? |
@victorhooi hi! Yes, currently it's expected since we are still having Polymer After the hybrid is released, the plan is to start working towards a Polymer 2-only version which will have the Polymer |
I am trying to use the Polymer-2 version in Chrome with the simple binding example and get
I find the following implementation in Polymer 1.0
Any idea how I could fix this in vaadin-grid-table.html to make progress? Edit: |
@nicolasr75 which branch/version of |
@Saulis Sorry, I forgot. I use 2.1-Polymer-2. |
@nicolasr75 can you double-check that? Try calling |
@Saulis You are right, somehow my packages were messed up. With a new project everything so far works as expected. Sorry for wasting your time. Keep up the good work! |
+1 |
We have migrated all other components to Polymer 2.0 except vaadin-grid. Question is which branch can be used right now, 2.1-polymer-2-rebased or something else. Also, which branch (Polymer 2.0 compatible) is working in IE 11? Thanks! |
@lchen2017 there's a |
@Saulis Thanks. Appreciate if you can update us on support for IE11. |
v3.0.0-alpha1 should work for IE11. Does not work for you? |
@manolo No, it doesn't work. |
what version of polymer are you using ? Are you compiling your javascript to ES5 ? |
@manolo It doesn't work with Polymer 2.0 when we use vaadin 2.1-polymer-2 code. We will try release v3.0.0-alpha1 and let you know. Thanks! |
Developers can use vaadin-grid with Polymer2 projects
See more on IDEA 210 vaadin-grid Polymer 2.0 support
Premilinary Steps: (by @Saulis)
In preparation for using<slot>
, place cells inside shadow root of<vaadin-grid>
<content>
for<slot>
and::content
to::slotted()
Separate "fixed" elements sections to improve UXundefined
values<style is="custom-style">
with<custom-style>
Templatizer
functionality to work with both v1 and v2Modify scroller internals to use a flexboxOther notable changes:
Polymer.dom(x).querySelectorAll(..)
returnsNodeList
instead ofArray
<slot>
without a name cannot have fallback/default contentPolymer.Settings.useNativeShadow
->Polymer.Settings.useShadow
Polymer.dom.flush()
no longer flushes mutation observers, they need to be explicitly flushed.target.click
:_onClick
inlisteners
block doesn't workThe text was updated successfully, but these errors were encountered: