Enterprise: Support configuring top level element

I think we do need this for other cases so the trick would be to just add an ids-enterprise top level class and let it cascade only after that. Would be a breaking change we can mitigate easily. Could also add it to initialize() when you call that (if people use it).

Would it be possible to add support for soho to add support for ignoring elements?
In our use-case we want app styled according to Soho, but we need a way to tell Soho css to ignore certain elements and it's descendants

e.g. elements with class would be ignored

.soho-ignore

perhaps :not() selector would be of help?

I'm not sure that would be easy @Fruko I guess we would have to add an entire second style sheet where we :not() EVERY single css rule? For example what if you use a tree class in there or a dropdown or anything else it could still cause problems.

I think the other way to do this is just not put on the ids-enterprise rule on that top level element and that would serve as a not.

<div class='ids-enterprise'>
   <!-- Soho / IDS stuff -->
</div>
<div class='anything-else-but-ids-enterprise'>
   <!-- Not Soho / IDS stuff -->
</div>

Thanks for looking into it @tmcconechy ! This and a couple other issues (which I will log) are preventing Infor Nexus from migrating to IDS (we're on a years-old forked version of Soho), so this would be a big help.

Cool yes enough use cases to add this. Will look into it soon. I think just requiring the top level element but may mean a 5.0 version just to follow semantic versioning with a small number of breaking changes.

@tmcconechy but what about scenario like this

    <div class="accordion ids-enterprise" data-demo-set-links="true" data-options="{'allowOnePane': false}">
      <div class="accordion-header">
        <a href="#"><span>Warehouse Location</span></a>
      </div>
      <div class="accordion-pane">
        <div class="accordion-content">
          <some-component-with-own-styles></some-component-with-own-styles>
        </div>
      </div>

given code above, how can we make sure that ids-enteprise css won't mess with "some-component-with-own-styles?

From my point of view adding root element to cascade css from is a good idea for a start, but I believe in order to make enteprise css usable, there has to be a way of making it not fiddle with other parts of apps, if :not selector is not an option, what about prefixing all ids-enterprise classes with ids-enterprise?

yeah i thought about prefixing all options with ids- but its a much more breaking change. Also not sure that it would solve this exact case if we just made it called ids-accordion-content.

For this exact case i think we could come up with something that negates any styling in the accordion-content but i think that would be a separate issue. And would have to do this component by component.

Im just doubting there is any good way to make a not-ids class that works on every single entire component no matter where you put it. So it's going to be more of a case by case thing for that.

Wonder if a more simple reset would help tho? Fx... ids-reset

• would set font, padding, margin and maybe a few more things back to document root?

Sort of a reverse reset? Might help in some cases but definitely not all?

that might do the trick

Ok will take a look along with this. Thats not as bad as i was expecting initially.

I like the idea of prefix with ids. Actually it's called "branding" concept. Definitely it's a breaking change but it should be the way to go for ids-enterprisd css structure in the future.

I agree have to weight the value over the breaking change.

Checked this further. It cant be done without a prefix added to the root. Was hoping i could find a way.
In the next gen project everything has prefixes and is self contained so this will not be an issue. Shelving this for now but not closing as we might need to do this on a major version

We have a solution in the 5.0 next version where each component is a web component with encapsulated css and all css is namespaced. This would satisfy this issue so closing

@tmcconechy that's great news! Is there a good way to track when this is generally available?

You can keep an eye on this project https://github.com/infor-design/enterprise-wc -> it is a ways off but sometime next year should have something released

Looks really promising!