作者:笑竹舞 | 来源:互联网 | 2023-05-18 17:58
MycolleagueandIarehavingatoughtimedecidingonabestpracticesapproachforie6,ie7suppor
My colleague and I are having a tough time deciding on a best practices approach for ie6, ie7 support for a site we're building. The site is for an older crowd, so not supporting these browsers is out of the question.
我和我的同事正在艰难地为我们正在构建的一个站点的ie6、ie7支持制定一个最佳实践方法。这个网站是针对老用户的,所以不支持这些浏览器是不可能的。
At the same time, we're trying to start incorporating modern coding practices into our work so we can get practice and fully understand capabilities. A specific area I want to touch on with you guys is handling fall backs for CSS3 backgrounds.
与此同时,我们正试图将现代编码实践融入到我们的工作中,以便我们能够得到实践并充分理解功能。我想和你们讨论的一个具体领域是处理CSS3背景的后退。
We have 2 choices here, if we're to use CSS3 backgrounds and not add extraneous wrapping tags for backgrounds:
如果我们使用CSS3背景而不为背景添加额外的包装标签,我们有两个选择:
- Use :after, :before etc. pseudo elements for adding multiple backgrounds to elements. (this is the choice we've made for now)
- 使用:after,:before等伪元素为元素添加多个背景。(这是我们现在做出的选择)
- Use CSS3 multiple background specifications
- 使用CSS3多重背景规范
This produces more elegant markup and is certainly a step in the right direction. But what about browsers that don't support these features?
这将产生更优雅的标记,而且无疑是朝着正确方向迈出的一步。但是那些不支持这些特性的浏览器呢?
Modernizr.js tells us to check for specific support and then write fallbacks:
Modernizr。js告诉我们检查具体的支持,然后写回:
Modernizr.load({
test: Modernizr.geolocation,
yep : 'geo.js',
nope: 'geo-polyfill.js'
});
However, we're not given much guidance on the actual fallbacks for specific features. So, in the case of something like CSS3 backgrounds, what would be an effective fallback strategy?
但是,我们没有得到关于特定特性的实际回退的指导。那么,在CSS3这样的背景下,什么是有效的退步策略呢?
Would we (for example) use jQuery to wrap those extra tags we need (ie btn-container, nav-container, etc.) around nav items, buttons and containers in order to have extra elements to add style attributes to?
我们(例如)会不会使用jQuery将我们需要的额外标签(如btn-container、nav-container等)包装在nav项目、按钮和容器周围,以便有额外的元素添加样式属性?
3 个解决方案