foundation-sites: Normalize does not set display block
What should happen?
normalize should set the <main> tag to display: block,
like it has done at version 6.4.4-rc1 with normalize.scss
What happens instead?
Nothing is set for the <main> tag. IE is known for not implementing/support
the main tag, so at least display: block have to be set to make it behave
like a div.
Possible Solution
- Consider using another vendor normalize
- Introduce your own normalization with:
main { display: block; }
Test Case and/or Steps to Reproduce (for bugs)
Use a <main> tag in IE with foundation and add for instance a background color.
Place some content inside the main and the background color will not be shown.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 19 (10 by maintainers)
If I may continue with the purpose of this issue and the problem that Foundation is facing.
We care more about our developer’s best interests than the struct following of the “browser normalization” approach. But on the other side, we want to rely on a watched and well-maintained project.
@necolas What is the maintenance status of
necolas/normalize.css? Is there someone that currently ensure a technological watch on the project? As you can see, many improvements has been made in the csstools’ version this year. Would you consider adding them to your version?@jonathantneal Developers generally don’t like separations in communities and projects, and most often it doens’t end very well. Do you think that creating a second
csstools/normalize.cssproject is the best solution? Would there be others options that would be in the best interest of the whole community? For example at Foundation we provide several CSS files so the user can pick the one that fit the best its needs.Would you mind helping me with the name? Naming things is hard. Right now it’s @csstools/normalize.css on npm and the README.md just calls it normalize.css, since they have the same initial git history.
I’ve immediately updated the README.md to call it csstools-normalize (following the sindresorhus convention) and I’ve added the opinionated styles (edit) in a separate file (sorry, was rushing typing). I can add the others after referencing the current necolas release. See https://github.com/csstools/normalize.css
Anything else I can do to help?
I’m really sorry to read that, Nicolas. I would love, love to be on good terms again. I understand if you’re not interested at this time, and I do hope it changes. Would you consider unblocking me from the project if I agree not to comment on any issues until you say it’s okay? It really sucks to not be un-included like that.
As for this thread; y’all pick the libraries that serve your needs best.
I think the issue of
body { margin: 0 }is a kind of tabs vs spaces thing. I tend to think normalize should stick to fixes, while many other intelligent people think certain opinions are practical.I would have personally expected people to “die on a hill” (*) for adding
* { box-sizing: border-box }before preservingbody { margin: 0 }but the later has obviously had a major influence on the project. I didn’t expect that. 😄@ncoden, totally understood. Please delete this message if you feel it’s aggravating.
@necolas @jonathantneal
Hello Guys, I’m happy to see you two there, but at first I have to make this very clear:
You will not start another fight.
@jonathantneal I just corrected my comment.