55岁属什么
|
56岁属什么
|
三省吾身是什么意思
|
三代试管是什么意思
|
千千结是什么意思
|
老婆妹妹叫什么
|
爷爷的爸爸叫什么
|
大便为什么是黑色的是什么原因
|
死亡是什么感觉
|
为什么女娲是一条蛇
|
奇美拉是什么
|
乳腺彩超什么时候做最准确
|
欣赏一个人是什么意思
|
手术后吃什么鱼伤口愈合快
|
为什么老是犯困
|
艾灰有什么作用和功效
|
梗塞灶是什么意思
|
湿气重去医院挂什么科
|
青霉素过敏可以吃什么消炎药
|
touch什么意思
|
dr拍片是检查什么的
|
梦见芹菜是什么意思
|
防字代表什么生肖
|
胸椎退行性变什么意思
|
房颤是什么
|
青蛇是什么蛇
|
梦游的人为什么不能叫醒
|
附件炎是什么症状
|
易孕期是什么时候
|
议论纷纷是什么意思
|
什么情况需要根管治疗
|
卤水是什么
|
结节性红斑是什么病
|
什么颜色最显白
|
上炕是什么意思
|
验孕棒什么时候测最准确
|
脑供血不足吃什么食物好
|
ckd是什么病
|
ctu是什么意思
|
送妈妈什么礼物好
|
非虫念什么
|
中位数什么意思
|
新生儿缺氧会有什么后遗症
|
什么是ct检查
|
振幅是什么意思
|
377是什么意思
|
耳毛念什么
|
白带黄绿是什么原因
|
前列腺吃什么食物调理
|
为什么来大姨妈会拉肚子
|
为什么会嗜睡
|
7月初二是什么星座
|
心什么什么什么
|
甘草长什么样子图片
|
为什么膝盖弯曲就疼痛
|
猫吃什么下奶最快最多
|
安抚是什么意思
|
乳头痛什么问题
|
饭后放屁多是什么原因
|
胃炎吃什么食物好得快
|
什么醒酒
|
后背疼挂什么科
|
水饮是什么意思
|
什么能代替润滑油
|
午餐吃什么
|
滢是什么意思
|
冥寿是什么意思
|
什么牌子的裤子质量好
|
什么网站可以看三节片
|
吃什么消除肺部结节
|
吃什么增强免疫力最快
|
抬头头晕是什么原因
|
为什么眼睛会有红血丝
|
肛裂用什么药
|
住房公积金缴存基数是什么意思
|
生理期是什么意思
|
嘴巴旁边长痘痘是为什么
|
雌二醇e2是什么意思
|
血铅是什么
|
fpd是什么意思
|
一个鱼一个完读什么
|
夜幕降临是什么意思
|
au9999是什么意思
|
海马炖什么好小孩长高
|
内招是什么意思
|
恩裳是什么档次的衣服
|
万岁是什么意思
|
胸痹是什么意思
|
脉搏90左右意味着什么
|
葛根长什么样子图片
|
没谁了是什么意思
|
香蕉水是什么
|
明矾是什么东西
|
寒窗是什么意思
|
不问世事什么意思
|
兰桂齐芳是什么意思
|
蝉吃什么东西
|
农转非是什么意思
|
被蜈蚣咬了有什么症状
|
胆结石是什么
|
为什么爱放屁
|
老是想睡觉是什么原因
|
未可以加什么偏旁
|
为什么睾丸一边大一边小
|
黑洞里面是什么
|
什么东西补血最快
|
溜溜是什么意思
|
离婚的女人叫什么
|
中医心脉受损什么意思
|
小拇指旁边的手指叫什么
|
脖子粗大是什么病的症状
|
多吃什么可以长头发
|
省略号的作用是什么
|
手为什么会脱皮
|
肺活量5000什么水平
|
啤酒和什么不能一起吃
|
查肝炎做什么检查项目
|
硼砂是什么东西
|
肺炎支原体感染吃什么药
|
水鱼煲鸡汤放什么药材
|
什么的东风填词语
|
疱疹是什么症状
|
梦见过河是什么意思
|
微波炉蒸鸡蛋羹几分钟用什么火
|
左边是心脏右边是什么
|
眼睛经常长麦粒肿是什么原因
|
89年属什么生肖
|
成吉思汗姓什么
|
舌强语謇是什么意思
|
肝病吃什么药
|
凤是什么意思
|
女性感染hpv有什么症状
|
煮虾放什么调料
|
掉头发吃什么药
|
鳏寡孤独是什么意思
|
rt什么意思
|
铁蛋白低吃什么可以补
|
青蛙喜欢吃什么
|
什么叫人格
|
子宫内膜c型什么意思
|
提心吊胆是什么意思
|
白带增多是什么原因
|
产后检查挂什么科
|
脑残是什么意思
|
shiraz是什么名字红酒
|
装模作样是什么生肖
|
古早是什么意思
|
静夜思是什么季节
|
表水是什么意思
|
alpaca是什么意思
|
腊肉炒什么菜最好吃
|
谷草转氨酶是什么意思
|
刺史相当于现在的什么官
|
露营需要准备什么东西
|
孕期血糖高可以吃什么水果
|
精液是什么味道
|
精明是什么意思
|
吩咐是什么意思
|
化疗后吃什么补白细胞
|
月经期间适合做什么运动
|
喜闻乐见什么意思
|
荆芥是什么菜
|
早搏有什么危害
|
左眉毛上有痣代表什么
|
春宵一刻值千金什么意思
|
男人吃什么壮阳
|
甲减有什么症状
|
什么火海
|
车厘子是什么季节的
|
糖尿病筛查做什么检查
|
四百多分能上什么大学
|
齁甜是什么意思
|
8月11日是什么星座
|
为什么睡觉总是做梦
|
胎膜早破是什么意思
|
唐氏综合症是什么
|
谨字五行属什么
|
一个月一个元念什么
|
肠胀气是什么原因
|
二甲苯是什么东西
|
什么是三伏天
|
pet什么意思
|
会字五行属什么
|
毛的部首是什么
|
夜场是什么工作
|
什么名字好听男生
|
osd是什么意思
|
腋下副乳有什么危害吗
|
什么是肝性脑病
|
立春之后是什么节气
|
流产什么样的症状表现
|
虾米是什么意思
|
感冒头晕吃什么药
|
手上脱皮是什么原因
|
白斑用什么药膏
|
流产会出现什么症状
|
心颤吃什么药效果好
|
generic是什么意思
|
敢爱敢恨是什么意思
|
幺蛾子是什么意思
|
为什么老是便秘
|
j是什么
|
闲鱼卖出的东西钱什么时候到账
|
2000年属龙的是什么命
|
痛风能喝什么饮料
|
息肉样增生是什么意思
|
绿豆芽不能和什么一起吃
|
什么食物养肝护肝最好
|
邦顿手表是什么档次
|
暖气是什么症状
|
什么的感受
|
对方忙线中什么意思
|
耳石症是什么症状
|
三高人群适合吃什么
|
半身不遂是什么意思
|
膀胱炎做什么检查能看出来
|
骶管小囊肿是什么意思
|
白芨主治什么病
|
发配是什么意思
|
住院医师是什么意思
|
嗓子哑了是什么原因
|
什么是陈皮
|
桃花灼灼什么意思
|
头上长了个包挂什么科
|
肝囊肿有什么危害
|
1969年什么时候退休
|
拉肚子低烧是什么原因
|
舌根放血有什么好处
|
头顶痛吃什么药效果好
|
痔疮吃什么药好得快
|
1958年属狗的是什么命
|
海扶治疗是什么
|
查性激素六项挂什么科
|
孕妇吃什么鱼最好
|
狮子吃什么
|
提辖相当于现在什么官
|
流涎是什么意思
|
乳房挂什么科
|
simon什么意思
|
无事不登三宝殿什么意思
|
梦见吃饭是什么预兆
|
嘴唇周围长痘痘是什么原因导致
|
小孩有口臭是什么原因引起的
|
2017年属鸡火命缺什么
|
送什么生日礼物给妈妈
|
柿子和什么不能一起吃
|
泮是什么意思
|
高祖父的爸爸叫什么
|
m是什么
|
乌鸡白凤丸有什么功效
|
陈赫是什么星座的
|
什么是符号
|
土豆不能和什么食物一起吃
|
pt是什么时间
|
eligible是什么意思
|
金贵肾气丸治什么病
|
抗ccp抗体高说明什么
|
slf是什么意思
|
多梦睡眠质量不好是什么原因
|
圆寂为什么坐着就死了
|
亚麻是什么植物
|
n表示什么
|
打下巴用什么玻尿酸最好
|
什么是刑事拘留
|
百度
Chromium Blog
News and developments from the open source browser project
Intent to Explain: Demystifying the Blink Shipping Process
Tuesday, November 12, 2019
If you’re a standards-curious web developer, you may have wondered how features get added to browsers, or even how the Chrome team decides what they will work on. You probably also have, at least at some point, thought to yourself “I have this urgent problem but I’ll have to work around it for the foreseeable future, because browsers are just too slow to bring in changes”. You may have even added some expletives when no one was around.
If that description sounds accurate, this is the post for you! This post will describe the Blink process, how browser engineers (both inside and outside of Google) use it in order to ship features in Chromium, what considerations are taken when deciding to ship a new feature, as well as some considerations that impact
what
features get worked on, and how you can play a role in all of this!
Project goals
The
Chromium project
is the open source project on which Chrome is built, and on which other browsers are also based: Samsung Internet, Opera, Brave, Vivaldi, and last (to join the project) but not least, Microsoft Edge. The project enables all those different browsers to share a single implementation of the web platform, and at the same time, keep their unique characteristics and focus.
Blink
is the rendering engine used by Chromium. It is the part of the project that descends from
WebKit
(the rendering engine Safari uses), and which is mostly (but not exclusively) responsible for the Chromium’s Web Platform implementation. The goal of Chromium and Blink inside it is to continuously improve the web platform as a whole.
How does Blink improve the web platform?
By improving its
predictability
through testing and infrastructure, making sure developers have to spend less of their time tackling browser-specific issues and more of their time… well, developing.
By
removing user hostile features
, features that increase the platform’s complexity or make its implementations less secure.
By
adding platform capabilities
that enable web developers to innovate and create web experiences that meet and exceed their users’ expectations and needs.
If we want the web to thrive in the long term, we need to make sure that our users consider it safe and pleasant to use, and that it supports all the capabilities developers need in order to easily make their users (and businesses) are happy.
Any improvement to the platform needs to take
backwards compatibility
and
cross-browser interoperability
into account. There’s a lot of web content out there that will never change. The risk of breaking some of it needs to be weighed against the user benefits of shipping that new feature or removing that risky old one. Similarly, in cases where Blink is the first engine to ship a feature or to remove it, we should make sure other browser vendors can follow. We do that by ensuring shipped features designs are widely reviewed, and have specifications and
tests
to guide future implementers.
The Chromium project is rather large, and is being worked on by many different entities. Therefore it needs to control which features get shipped, while being even-handed in that decision process. We achieve that through a simple process that guides contributors as they evolve the platform to ensure maximum long-term compatibility and interoperability.
What features get worked on?
Chromium is an open source project that’s being worked on by over 2000 engineers from ~55 different organizations. Of course, Google is responsible for the bulk of Chromium - 92% of commits to the project (
data
) come from Google, although about 20% of contributors are not Google-affiliated.
With a project of this magnitude, each of the involved companies and contributors are naturally pushing their own slightly different agenda and priorities. Even within Google’s Chrome team there are multiple ways to prioritize which problems are most urgent to tackle and solve. One area that is consistent, is that we work with the ecosystem and developer partners to understand and address their needs. We do that by creating compatibility dashboards, collaborating with frameworks, and observing development patterns in the wild.
The
MDN survey
is a great example of how the ecosystem can help shape the priorities that a browser vendor has. We’re still in the process of analyzing the results, but it was clear that compatibility is a top priority for developers and we will commit to keep improving on it. We also plan to create more ways to gather structured data on developer needs and hardships.
As you can imagine, with all these priorities from different contributors, it's important for us to be clear about how a feature goes from inception to shipping.
So, what are the typical phases of creating a new web platform feature and shipping it in Chromium?
The very first step before getting started would be to figure out what we need to be working on and which user or developer problems are the most burning ones. That is typically done by talking to partners, looking at current development patterns and consulting with web developers and framework authors to get a better understanding of what the platform can do better to address their and their users’ needs.
Once we know which problem we want to tackle, we can start incubating it!
What does “incubating” mean?
Over the years, we found that the best way to design and prototype a new platform feature is through
incubation
- getting a strong grasp of the use cases a feature is trying to solve as a first step, and then rapidly iterating over the design in a public forum that includes browser engineers and domain experts. Only once we are certain that a feature solves important use-cases and have high confidence that it solves it the right way, we bring that feature to an official track at a Standard Development Organization, such as a W3C Working Group, the WHATWG, or TC39.
Not all incubations turn up to be standards though. Some incubations fail and some prototypes never make it out to the hands of users. That is perfectly fine and by design. The web platform cannot afford features that don’t solve real user or developer problems to creep in, and we want to make sure those features never make it to be a permanent part of the platform.
Step 1 - Initial research
At this phase, we establish a better understanding of the problem space, by gathering up the specific use-cases we want our future solution to tackle and the constraints under which the solution must operate.
At the end of that phase, engineers are expected to publish an
explainer
that outlines the above, and maybe have a very rough sketch of what a solution may look like. The explainer is published in a relevant public forum (e.g. the
WICG discourse
) in order to solicit feedback from the web community at large. Such feedback can include missed-out use-cases, further constraints that can impact the design, or simply statements of support for solving the problem.
It’s important at this stage to focus on the problem, and not over-index on any one possible solution - and this is one of the places we haven’t always been perfect.
Step 2 - Design & Prototype
Now that we have better grip of the problems we’re trying to solve and the constraints in which we operate, we can start designing the feature and what it may look like. Ideally, the design team would include browser engineers from interested vendors as well as problem space experts from the web developer or framework developer community.
Once we have an initial rough design, it might be a good idea to start building and committing code (behind a flag and turned off by default) in order to better understand the solution’s feasibility and complexity.
That’s when engineers should send out an “
Intent to Prototype
” email to
blink-dev
(previously, “Intent to Implement”), in order to notify the relevant code owners that work is underway in that area. Note that such an intent doesn’t mean that the feature is shipping soon, or that it will ship at all for that matter. It just means that this is a problem space that’s being explored, and code is landing to that end.
That’s also a good point in time to make sure the feature will get a wider review, by filing for a
TAG review
.
Step 3 - Experiment & iterate
Once code starts to land behind a flag, it’s a good time for interested web developers to start playing around with the solution by turning on the feature flag and testing it out.
Feedback on the initial implementation is critical in order to make sure the eventual design would work well for developers and users alike.
For some features, such experimentation is enough for developers to get a good handle on what’s the solution looks like, and how well it addresses the problem.
In other cases, it’s critical to gather data from the field regarding the solution, to see how well it works in broader deployment to fulfill user’s needs, or get a better understanding of its performance characteristics at scale.
Step 3.5 - Origin Trial
In those cases, a browser engineer can request an
Origin Trial
(by sending out an
Intent to Experiment
email), which enables interested developers to test the feature out in broader deployment to users who have not turned on the feature flag. Once an Origin Trial is in place, developers can register for the trial, and enable the feature (in production) for their domains. That enables them to gather data on the user impact of the feature, and report it back to the design team, confirming or refuting their assumptions regarding the solution’s viability.
Note that an Origin Trial is a temporary experiment, and there’s a good chance that the feature will significantly change before it will be enabled by default, or even that the effort will be dropped altogether. Developers interested in participating should take that into account, and not rely on the feature being available to their users beyond the scope of the trial.
Step 4 - ship it!
Once the previous steps were completed with success and the team believes the feature is ready to be turned on by default, that’s when they can submit an
Intent to Ship
.
That’s a part of the process that’s
a bit more strict
.
In order to ship a feature by default, engineers need approval for the feature to ship from 3 API owners.
What’s an “API owner”?
API owners
are a set of trusted Chromium engineers, who are responsible for enforcing the Blink process guiding principles. Each feature we’re trying to ship has some user and developer benefits, otherwise we probably wouldn’t be working on it. Shipping new features can introduce interoperability risks, if other browsers don’t follow us. The API owners are tasked with applying our
compatibility
and
interoperability
principles and help evaluate each shipping feature with regards to its risk/benefit tradeoff. They then provide their approval on “Intent to Ship” threads for new shipping features, if they think the benefits outweigh the risks. Those approvals are provided in the form of “LGTM” (“Looks Good To Me”) replies on intent threads.
Note that LGTMs are not required for Intent to Prototype. For an Intent to Experiment, approval from a single API owner is sufficient, as the risk they pose is fairly contained.
As part of the “Intent to Ship” request, chromium engineers need to provide clear signals regarding the risk and benefit tradeoff of the feature.
The feature needs to have a solid specification and a comprehensive cross-browser test suite in order to minimize interoperability risk.
Signals from other browser vendors as well as from wide review forums (such as the TAG) are taken into account, alongside signals from the web developer community and partners who are planning to use the feature.
If the feature went through an Origin Trial, a report outlining the results is also important to better understand the benefits.
Note that the fact that an “intent to ship” is sent indicates the team’s estimate of the feature being ready to ship, but it does not necessarily mean that the feature will ship shortly, or at all.
Some features take a long time to go through the intent process, in order to prove that the risk they pose is low enough to justify shipping. Others get held up addressing feedback from other vendors or from wide-review forums.
In other (rare) cases, features can be rejected by the API owners, and their proponents then need to look for alternative ways to resolve the problem, which won’t hit the same concerns that got their initial intent rejected.
Removing features
Finally, while adding new feature certainly grabs most people’s attention, an equally important part of the intent process is to deprecate and remove legacy web platform features. In those cases, the main risk is breaking existing content, and the benefits are typically around improving user’s security, privacy and performance. The project’s willingness to take some compatibility risk and remove features is critical to our risk/benefit calculus also when launching features first - if we got it wrong and late feedback causes us to change course, we typically can figure out a path to deprecate those features to get us back on track to interoperability.
Summary
The Chromium’s project goal is to make sure the web platform remains a healthy and successful platform.
For that, we believe the platform needs to make significant progress in the face of shifting developer and user expectations, as well as adapt to the changing market forces and constraints. At the same time, we need that progress to be done in a responsible manner both inside the Chromium project and when it comes to our collaboration with the wider ecosystem.
The Blink process’ role is to keep the balance between those different requirements, and to help ensure the web is a thriving platform for generations to come.
Posted by Yoav Weiss, Wrangler of processes and Advocate of developers.
Labels
$200K
1
10th birthday
4
abusive ads
1
abusive notifications
2
accessibility
3
ad blockers
1
ad blocking
2
advanced capabilities
1
android
2
anti abuse
1
anti-deception
1
background periodic sync
1
badging
1
benchmarks
1
beta
83
better ads standards
1
billing
1
birthday
4
blink
2
browser
2
browser interoperability
1
bundles
1
capabilities
6
capable web
1
cds
1
cds18
2
cds2018
1
chrome
35
chrome 81
1
chrome 83
2
chrome 84
2
chrome ads
1
chrome apps
5
Chrome dev
1
chrome dev summit
1
chrome dev summit 2018
1
chrome dev summit 2019
1
chrome developer
1
Chrome Developer Center
1
chrome developer summit
1
chrome devtools
1
Chrome extension
1
chrome extensions
3
Chrome Frame
1
Chrome lite
1
Chrome on Android
2
chrome on ios
1
Chrome on Mac
1
Chrome OS
1
chrome privacy
4
chrome releases
1
chrome security
10
chrome web store
32
chromedevtools
1
chromeframe
3
chromeos
4
chromeos.dev
1
chromium
9
cloud print
1
coalition
1
coalition for better ads
1
contact picker
1
content indexing
1
cookies
1
core web vitals
2
csrf
1
css
1
cumulative layout shift
1
custom tabs
1
dart
8
dashboard
1
Data Saver
3
Data saver desktop extension
1
day 2
1
deceptive installation
1
declarative net request api
1
design
2
developer dashboard
1
Developer Program Policy
2
developer website
1
devtools
13
digital event
1
discoverability
1
DNS-over-HTTPS
4
DoH
4
emoji
1
emscriptem
1
enterprise
1
extensions
27
Fast badging
1
faster web
1
features
1
feedback
2
field data
1
first input delay
1
Follow
1
fonts
1
form controls
1
frameworks
1
fugu
2
fund
1
funding
1
gdd
1
google earth
1
google event
1
google io 2019
1
google web developer
1
googlechrome
12
harmful ads
1
html5
11
HTTP/3
1
HTTPS
4
iframes
1
images
1
incognito
1
insecure forms
1
intent to explain
1
ios
1
ios Chrome
1
issue tracker
3
jank
1
javascript
5
lab data
1
labelling
1
largest contentful paint
1
launch
1
lazy-loading
1
lighthouse
2
linux
2
Lite Mode
2
Lite pages
1
loading interventions
1
loading optimizations
1
lock icon
1
long-tail
1
mac
1
manifest v3
2
metrics
2
microsoft edge
1
mixed forms
1
mobile
2
na
1
native client
8
native file system
1
New Features
5
notifications
1
octane
1
open web
4
origin trials
2
pagespeed insights
1
pagespeedinsights
1
passwords
1
payment handler
1
payment request
1
payments
2
performance
20
performance tools
1
permission UI
1
permissions
1
play store
1
portals
3
prefetching
1
privacy
2
privacy sandbox
4
private prefetch proxy
1
profile guided optimization
1
progressive web apps
2
Project Strobe
1
protection
1
pwa
1
QUIC
1
quieter permissions
1
releases
3
removals
1
rlz
1
root program
1
safe browsing
2
Secure DNS
2
security
36
site isolation
1
slow loading
1
sms receiver
1
spam policy
1
spdy
2
spectre
1
speed
4
ssl
2
store listing
1
strobe
2
subscription pages
1
suspicious site reporter extension
1
TCP
1
the fast and the curious
23
TLS
1
tools
1
tracing
1
transparency
1
trusted web activities
1
twa
2
user agent string
1
user data policy
1
v8
6
video
2
wasm
1
web
1
web apps
1
web assembly
2
web developers
1
web intents
1
web packaging
1
web payments
1
web platform
1
web request api
1
web vitals
1
web.dev
1
web.dev live
1
webapi
1
webassembly
1
webaudio
3
webgl
7
webkit
5
WebM
1
webmaster
1
webp
5
webrtc
6
websockets
5
webtiming
1
writable-files
1
yerba beuna center for the arts
1
Archive
2025
Jul
Jun
May
Jan
2024
Dec
Aug
Jun
May
Apr
Mar
Feb
2023
Nov
Oct
Sep
Aug
Jun
May
Apr
Feb
2022
Dec
Sep
Aug
Jun
May
Apr
Mar
Feb
Jan
2021
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2020
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2019
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2018
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2017
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2016
Dec
Nov
Oct
Sep
Aug
Jun
May
Apr
Mar
Feb
Jan
2015
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2014
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2013
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2012
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2011
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2010
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2009
Dec
Nov
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2008
Dec
Nov
Oct
Sep
Feed
Follow @ChromiumDev
Give us feedback in our
Product Forums
.
大浪淘沙下一句是什么
脑干出血是什么原因
孕妇做无创是检查什么
狗属于什么类动物
什么是五常大米
痔疮长什么样子的图片
雨打棺材是什么征兆
香醋是什么醋
斐乐是什么档次
衣冠禽兽指什么生肖
小妮子什么意思
扁平疣用什么药膏
青核桃皮的功效与作用是什么
硫酸对人体有什么危害
破屋坏垣适合干什么
字字珠玑是什么意思
孩子拉肚子吃什么食物好
4月12号是什么星座
深圳市长是什么级别
世界上最深的湖泊是什么
cd ts 什么意思hcv7jop4ns8r.cn
丹参的功效与作用是什么hcv9jop0ns8r.cn
明天有什么考试hcv9jop7ns2r.cn
假正经是什么意思hcv9jop5ns0r.cn
斑斓是什么意思hcv8jop6ns0r.cn
手掌很红是什么原因hcv8jop5ns8r.cn
omega是什么意思hcv8jop9ns8r.cn
月经前一周是什么期hcv8jop9ns8r.cn
dos是什么hcv8jop1ns9r.cn
塞飞洛是什么档次的包hcv7jop9ns9r.cn
王为念和王芳什么关系zsyouku.com
小腿疼痛什么原因引起的hcv8jop1ns2r.cn
晚上喝红酒有什么好处和坏处hcv9jop7ns9r.cn
01年属什么的hcv8jop8ns5r.cn
肝胆相照是什么生肖hcv8jop7ns9r.cn
c反应蛋白什么意思hcv9jop1ns1r.cn
冬至穿什么衣服hcv8jop2ns7r.cn
什么是微单相机hcv8jop1ns0r.cn
局灶肠化是什么意思hcv7jop6ns5r.cn
口臭吃什么好hkuteam.com
百度
