Skip to content

Default themes in Magento2 CE contain EE styling #2640

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

Closed
ivanweiler opened this issue Dec 8, 2015 · 10 comments
Closed

Default themes in Magento2 CE contain EE styling #2640

ivanweiler opened this issue Dec 8, 2015 · 10 comments
Labels
Area: Frontend bug report Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@ivanweiler
Copy link

Hello all,

Blank and Luma theme in Magento 2.0.0. CE include some styling from EE modules, for example:
https://github.com/magento/magento2/blob/develop/app/design/frontend/Magento/luma/Magento_Rma/web/css/source/_module.less

From commit it seems it's some kind of fix for EE 2d189de
but now generated css files in CE contain styling that is never used :(

Regards, Ivan

@alankent
Copy link

alankent commented Dec 8, 2015

This one deserves a blog post - there is a reason why, but I also would love feedback/ideas on how to make it better. I will try to get a blog post up and post the link here "shortly".

@davidalger
Copy link
Member

@alankent I'd be curious to hear the why behind this one as well. It seems rather odd and feels that surely there's got to be some way, right? But I think I may know the reason behind it without even asking. Maybe EE should ship with a coupe themes which use the CE themes as parent so it can have working theme examples in addition to the core module css? :)

@alankent
Copy link

alankent commented Dec 9, 2015

I have written up some things and ideas in this area on my blog at http://alankent.me/2015/12/09/even-better-themes-for-magento-2-seeking-feedback/ - in summary, putting some of the EE styles into Luma was the less evil solution, until we get a little more functionality into themes. Feedback welcome!

@maksek
Copy link
Contributor

maksek commented May 9, 2016

Hi @ivanweiler, do you want keep the topic or we are ok to close it?

@ivanweiler
Copy link
Author

Hello Max,

It's not really solved since unneeded styling is still part of CE, now we only know why it is there (mentioned less evil solution) :) I don't know if something is changed in latest commits, but I see that EE less files are still in CE themes, so they're most likely still compiled in final CE css.

If it's not doable at this point maybe this should be feature request or similar, since it should be solved on the long run. Number of EE modules is growing, so eventually there will be more and more unused css in CE.

Regards, Ivan

@tomislavbilic
Copy link

Issue of "removing unnecessary styling" should not, by all means, fit into "undoable" category. :)

@pboisvert
Copy link

Chuck--passing this one to you as unused code though small is a performance issue especiqlly if it grows over time.

@MomotenkoNatalia
Copy link
Contributor

Hi all!

We have an internal ticket regarding this problem - MAGETWO-62161.

@MomotenkoNatalia MomotenkoNatalia added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Dec 13, 2016
@choukalos choukalos removed their assignment Feb 21, 2017
@magento-engcom-team magento-engcom-team added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report Area: Frontend Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Sep 11, 2017
@magento-engcom-team magento-engcom-team added the Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed label Oct 23, 2017
@magento-engcom-team
Copy link
Contributor

@ivanweiler, thank you for your report.
We've created internal ticket(s) MAGETWO-62161 to track progress on the issue.

@magento-engcom-team magento-engcom-team added 2.1.x Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Oct 23, 2017
@magento-engcom-team
Copy link
Contributor

Hi @ivanweiler thank you for your report. Reported issue does not affect product functionality. But this is good improvement to have. We are closing the issue for now, but feel free submit a pull request with improvement

@magento magento locked and limited conversation to collaborators Mar 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Area: Frontend bug report Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests