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
enhancement: allow class name other than "layer" #204
Comments
+1 from me on this. If nobody vetoes, I'd completely remove the JS-side class name requirement. In my opinion, the script should be CSS-agnostic. |
… scene element a layer. Resolves issue #204
No vetoes received, have implemented this suggestion. Thank you! :) |
This modification broke my code. The @lupos idea was to be able to rename the class and not pick up the first descending elements. Similar example code:
|
Is there a reason you need to use containers instead of directly assigning the class names to the layer elements? I could implement an optional class selector for fringe cases like yours if there's no other solution. |
This modification broke my code as well. This doesn't work for complicated HTML structure. For example I have three different containers which are used for styling and by other JS UI plugins. And I simply can't move the Parallax layer elements to the top of this structure. I propose overriding layer elements only there are no elements with class |
Very good call, sorry to have caused such an inconvenience to you. Would that work for you, @amateur and @caiotarifa |
@RROrg, yes, it works for me. Thanks! |
@RROrg, I think so. Thanks! |
Please try the latest commit on master :) |
It works great! Thanks a lot. |
Thanks for your patience and understanding, all! ❤️ |
So I'm using this is a much larger project and attempting to name space all css classes and
layer
stands out as a fairly generic name. It's unlikely to actually cause an issue but it would be great to be able to pass in an alternative layer class name or a prefix ('my-custom-layer') so the library doesn't dictate code style in anyway.The text was updated successfully, but these errors were encountered: