Microsoft Edge joins Google, Mozilla, Samsung Internet, Igalia and the vast web community to launch a new initiative called "The Web We Want" dedicated to promoting open web and innovative development.
"The Web We Want" is an open initiative that aims to provide a platform for web developers and designers (or anyone who builds content for the web) to tell browser vendors directly what features we should focus on. The core question we asked is: If you could wield your wand to change any aspect of your web platform, what would you choose? What problems have you encountered in web development that need to be solved? What tools need improvement or build to better help you get the job done? What do you think should be supported natively but not currently? These are just some questions about thinking about how to submit ideas to the initiative.
Some of the submissions we currently receive cover a wider range of issues from specific feature requests to web platforms:
- I hope the browser can automatically fix the accessibility problems that can be repaired automatically
- Hope to improve HTML forms
- Hope to save/load debugger status
- Hope to achieve high-performance width and height CSS transitions
- Hope to put accessibility tools first
This is just a microcosm of the feedback we have received. You can browse the full list.
Why should you submit your thoughts to "The Web We Want"?
This is an opportunity to get your voice heard and help us determine the future direction of the web platform. After submitting your question or feature, we will determine whether your requirements can be directly addressed by the browser manufacturer, or whether more scope is required and suitable for discussion of Web standards.
This is an opportunity for us to step back and reevaluate the direction of the web’s future and identify the gaps that make web development difficult at the moment.
How to participate?
You can participate in several different ways, and “The Web We Want” contains several different components. First, think about what you think browser vendors should fix, and submit your ideas at webwewant.fyi. This is probably all you want to do, and it's great! We want to get any and all feedback about the platform, and we have professionals from different browsers that are constantly paying attention to submissions.
The second optional aspect of “The Web We Want” is a great way to get involved in the web community and try to speak publicly. We have been running "The Web We Want" as a community-centric panel session at conferences around the world.
If you submit your ideas and participate in one of our events, your submission may be selected and give a 3-5 minute lightning speech to the review team during the session, like an issue of “Smart Winners” but targeting the technical field. The live session we hold is a way to get feedback and opinions from industry experts such as Rachel Andrew, Jen Simmons, Miriam Suzanne and Marcy Sutton.
Even if you don’t attend one of these events in person, you can still participate! We want to consider that not everyone can attend the meeting, so if your submission is selected and you say you don’t attend the event, you will have the opportunity to record your lightning speech ahead of time, which we will include in the live session.
The on-site session ended with the judges discussing and deciding on the most urgent "needs" raised during the session. We also have a community voting session that allows event viewers to rank what they think browser manufacturers (or standards bodies) need to pay attention to the most. Even if you don’t attend events, you can still vote on the website to choose your favorite “needs” and share them on social media.
So far, we have held sessions at An Event Apart DC, Smashing Conf and View Source, and community engagement and group discussions on needs are amazing. If you are hosting a party or conference and are interested in hosting this session, please contact Stephanie Stimacor or Aaron Gustafson.
The Web We Want
We are in a stage of the web platform, and browser vendors and standards bodies are eager to understand what web developers and designers need in the platform. We need to know where to invest resources. Visit Web We Want and let us know what you think the web platform needs so that we can shape the future of the web together.
The above is the detailed content of Building the Web We Want. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

CSScounterscanautomaticallynumbersectionsandlists.1)Usecounter-resettoinitialize,counter-incrementtoincrease,andcounter()orcounters()todisplayvalues.2)CombinewithJavaScriptfordynamiccontenttoensureaccurateupdates.

In CSS, selector and attribute names are case-sensitive, while values, named colors, URLs, and custom attributes are case-sensitive. 1. The selector and attribute names are case-insensitive, such as background-color and background-Color are the same. 2. The hexadecimal color in the value is case-sensitive, but the named color is case-sensitive, such as red and Red is invalid. 3. URLs are case sensitive and may cause file loading problems. 4. Custom properties (variables) are case sensitive, and you need to pay attention to the consistency of case when using them.

Theconic-gradient()functioninCSScreatescirculargradientsthatrotatecolorstopsaroundacentralpoint.1.Itisidealforpiecharts,progressindicators,colorwheels,anddecorativebackgrounds.2.Itworksbydefiningcolorstopsatspecificangles,optionallystartingfromadefin
