为什么浏览器厂商制作自己的css属性? [英] Why do browser vendors make their own css properties?

查看:105
本文介绍了为什么浏览器厂商制作自己的css属性?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


  • 浏览器供应商为什么制作自己的
    css属性,即使他们知道这些属性
    在通过w3c之前不会通过w3c验证?

  • 目的是什么?是为自己的
    测试,还是为web开发人员,还是
    向世界展示浏览器功能
    和W3C组织
    和W3C的CSS开发团队? li>
  • 它是一个测试版的
    演示吗?

  • 如果我现在使用任何浏览器
    ,他们可以删除该属性


  • 例如:



    https://developer.mozilla.org/en/CSS_Reference / Mozilla_Extensions

    解决方案


    • 负责任的浏览器供应商知道几年后网络的外观。我不知道你在哪里得到不通过部分。

    • 这是关于为现代和未来浏览器设计网络的工具。

    • 是的

    • 是和否,他们不太可能会取消对扩展程序部分的支持。



    W3C正在考虑的是语法。让我们以梯度为例:

      -webkit-gradient(
    linear,
    left bottom,
    left top,
    color-stop(0.2,rgb(86,45,199)),
    color-stop(0.6,rgb(112,72,239))

    -moz-linear-gradient(
    center bottom,
    rgb(86,45,199)20%,
    rgb(112,72,239)60%

    这两个代码生成相同的渐变。如你所见,没有标准的过程,语法对于webkit和基于mozilla的浏览器来说都是令人困惑和不同的。



    但是让我们想象在两三年内,已经完成了。现在你只需要为标准添加另一行代码。

     渐​​变:center bottom #colorFrom opacityFrom #colorTo opacityTo; 

    现在这两个引擎都会理解渐变效果,如果在扩展之后指定,最后一个成为解释的人。


    • Why do browser vendors make their own css properties, even they know these properties will not pass the w3c validation before approved and added by w3c?
    • What is the purpose? Is for their own testing, or for web developers, or to demonstrate browser capabilities to the world and to the W3C organizations and to CSS development team of W3C?
    • is it like a beta version of demonstration?
    • if i use any browser specific for now can they remove that property's support from future versions.will i have to edit my css in future

    For example:

    https://developer.mozilla.org/en/CSS_Reference/Mozilla_Extensions

    解决方案

    • Responsible browser vendors (the big ones, excluding IE), know what the web will look a few years later. I don't know where you get the "not pass" part. They only implement things the browsers will support in a few years
    • It's about giving the tools to design the web for modern and future browsers.
    • Yeah, we can say it's a beta.
    • Yes and no, it's unlikely they will remove support for the extensions part.

    What the W3C is thinking about is the syntaxis. Let's take gradient for an example:

    -webkit-gradient(
        linear,
        left bottom,
        left top,
        color-stop(0.2, rgb(86,45,199)),
        color-stop(0.6, rgb(112,72,239))
    )
    -moz-linear-gradient(
        center bottom,
        rgb(86,45,199) 20%,
        rgb(112,72,239) 60%
    )
    

    Both these codes generate the same gradient. As you can see, there's no standard procedure, the syntaxis is both confusing and different for webkit and mozilla based browsers.

    But let's imagine in two or three years, the implementation is done. Now you just have to add another line of code for the standard.

    gradient: center bottom #colorFrom opacityFrom #colorTo opacityTo;
    

    Now both engines will understand the gradient statment and if it's specified after the extension ones, this last one will be the one to interpret.

    这篇关于为什么浏览器厂商制作自己的css属性?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆