什么情况下吃奥司他韦
|
乳腺增生什么意思
|
朱元璋为什么不杀朱棣
|
液体变固体叫什么
|
指导员是什么级别
|
上帝叫什么名字
|
送老师什么礼物
|
越南讲什么语言
|
女鼠和什么属相最配对
|
柯萨奇病毒是什么病
|
属鸡与什么属相最配
|
膝盖后面叫什么
|
考研复试考什么
|
配偶什么意思
|
右侧上颌窦粘膜增厚是什么意思
|
勃起不坚硬吃什么药
|
近亲是什么意思
|
王不见王是什么意思
|
梦见莲藕是什么意思
|
人言可畏是什么意思
|
西瓜有什么功效和作用
|
蜜糖冲水喝有什么功效
|
针清是什么
|
戴珍珠手链有什么好处
|
牙龈出血什么原因
|
母亲是o型血孩子是什么血型
|
借记卡是什么卡
|
猫来家门口有什么预兆
|
鸿字五行属什么
|
摆架子是什么意思
|
来大姨妈不能吃什么
|
总恶心是什么原因
|
左附件囊肿注意什么
|
什么叫边界感
|
糜烂性胃炎有什么症状
|
什么食物降火
|
廾是什么意思
|
药店最怕什么样的举报
|
保底工资是什么意思
|
皮肤一块白一块白的是什么原因
|
连长是什么级别
|
血脂高吃什么药好
|
10月是什么季节
|
雷诺综合征是什么病
|
玉帝和王母是什么关系
|
甲状腺低是什么意思
|
黄金的动物是什么生肖
|
孤臣是什么意思
|
中午12点半是什么时辰
|
1964年是什么年
|
不是你撞的为什么要扶
|
icloud是什么
|
玫瑰花泡茶有什么功效
|
8月25号是什么日子
|
什么瓜不能吃脑筋急转弯
|
阴骘什么意思
|
什么是强直性脊柱炎
|
睡觉起来头晕什么原因
|
谷氨酰转肽酶高什么原因
|
新生儿上户口需要什么资料
|
胃酸想吐是什么原因
|
紧急避孕药什么时候吃
|
肠胃不好吃什么药好
|
11月21是什么星座
|
田宅宫是什么意思
|
四相是什么意思
|
jeep是什么牌子
|
文武双全是什么意思
|
办护照需要什么条件
|
双开什么意思
|
肠道长息肉是什么原因造成的
|
什么舌头
|
玻璃属于什么垃圾
|
什么食物吃了会胀气
|
失眠吃什么好
|
宫腔镜检查后需要注意什么
|
内急是什么意思
|
蛇怕什么家禽
|
杜仲有什么功效
|
女生喜欢吃酸说明什么
|
红细胞低是什么原因
|
情人节送妈妈什么花
|
打马赛克是什么意思
|
乙肝第二针最晚什么时候打
|
喜欢紫色的人是什么性格
|
9月8号是什么星座
|
做梦梦见大火是什么意思
|
茱萸是什么
|
吃什么补血快
|
女性更年期挂什么科
|
大保健什么意思
|
坐飞机不能带什么物品
|
火龙果什么人不能吃
|
球镜度数是什么意思
|
帝王术是什么意思
|
钓是什么意思
|
决明子泡水喝有什么好处
|
大电念什么
|
月经不来吃什么药
|
睡觉头晕是什么原因引起的
|
开导是什么意思
|
知性是什么类型的女人
|
河南是什么气候
|
做生化是检查什么的
|
蝙蝠屎是什么中药
|
吕布为什么要杀董卓
|
鲍鱼吃什么
|
女性阳性是什么病
|
为什么禁止克隆人
|
梦见别人结婚是什么征兆
|
甲状腺囊实性结节是什么意思
|
金火是什么生肖
|
神经内科主要看什么病
|
吃什么容易放屁
|
鸡犬不宁是什么意思
|
头皮发痒是什么原因引起的
|
气血亏虚什么症状
|
蛋白质用什么试剂鉴定
|
呼吸道感染一般用什么消炎药
|
96年五行属什么
|
spf是什么意思
|
kappa属于什么档次
|
10月15号是什么星座
|
心火旺吃什么中成药
|
6月7号是什么星座
|
com代表什么意思
|
字字珠玑是什么意思
|
癫痫是什么
|
lmy是什么意思
|
松鼠尾巴有什么作用
|
水鱼煲鸡汤放什么药材
|
孩子不好好吃饭是什么原因
|
伊拉克是什么人种
|
基底是什么意思
|
什么门永远关不上
|
rsa胎位是什么意思
|
吃什么能消除子宫肌瘤
|
人的反义词是什么
|
狼吞虎咽什么意思
|
总三萜是什么
|
羽字五行属什么
|
什么人容易得多囊卵巢
|
这是什么表情包
|
果冻是什么意思
|
不停的放屁是什么原因
|
03年是什么命
|
吃什么降低胆固醇
|
合菜是什么
|
牙疼有什么好办法
|
一直打嗝是什么原因
|
未加一笔是什么字
|
丝绦是什么意思
|
牛仔裙配什么上衣好看
|
叶韵是什么意思
|
牛黄清心丸治什么病
|
认识是什么意思
|
放化疗期间吃什么好
|
身份证后四位是什么意思
|
拉格啤酒是什么意思
|
妇科假丝酵母菌是什么病
|
怕老婆的男人说明什么
|
天德是什么意思
|
怡字五行属什么的
|
太阳为什么能一直燃烧
|
眩晕症是什么原因引起的
|
包臀裙配什么上衣
|
身心交瘁什么意思
|
立碑有什么讲究和忌讳
|
山鬼是什么
|
肠胃不好喝什么奶粉好
|
精气神是什么意思
|
来大姨妈血块多是什么原因
|
男士睾丸疼是什么原因
|
公立医院和私立医院有什么区别
|
奇怪的什么
|
血糖高检查什么项目
|
一帘幽梦是什么意思
|
水的ph值是什么意思
|
知了的学名叫什么
|
手不释卷的释是什么意思
|
梦见梯子是什么意思
|
睡觉手麻木是什么原因
|
肠炎不能吃什么东西
|
脚趾第二个比第一个长有什么说法
|
孙耀威为什么被封杀
|
双向情感障碍是什么
|
西昌火把节是什么时候
|
吃羊肉不能吃什么水果
|
fancl是什么品牌
|
ysl属于什么档次
|
子宫糜烂是什么症状
|
梦见和死去的亲人说话是什么意思
|
脚底拔罐对女人有什么好处
|
9个月宝宝玩什么玩具
|
一意孤行是什么意思
|
什么止咳效果最好最快
|
燕窝什么人不适合吃
|
女人喜欢什么类型男人
|
绿色痰是什么原因
|
纳字五行属什么
|
宿醉是什么意思
|
原教旨主义是什么意思
|
为什么有白头发
|
子宫下垂有什么症状
|
为什么会得血管瘤
|
梦见楼塌了是什么意思
|
media是什么意思
|
ifashion是什么意思
|
胃胀不消化吃什么药
|
花椒有什么作用
|
颈椎轻度退行性变是什么意思
|
德国纳粹是什么意思
|
手的皮肤黄是什么原因
|
易经和周易有什么区别
|
喝蜂蜜水有什么好处和坏处
|
关帝是什么神
|
svip和vip有什么区别
|
果肉属于什么组织
|
糠是什么东西
|
偏头痛吃什么药效果好
|
什么是紫河车
|
拿的起放的下是什么意思
|
讣告是什么意思
|
pd是什么
|
怀孕什么时候吃鹅蛋最好
|
舌苔黑是什么病
|
咳嗽可以吃什么水果
|
瓜子脸适合剪什么发型
|
生是什么结构的字
|
吡唑醚菌酯治什么病
|
体外是什么意思
|
17是什么意思
|
牛奶什么时候喝最好
|
转氨酶高是什么情况
|
dr检查是什么
|
为什么乳头会有白色分泌物
|
吃什么补心脏供血不足
|
聊胜于无的聊是什么意思
|
芒果对身体有什么好处
|
德字五行属什么
|
电解质氯高是什么原因
|
什么是0
|
456什么意思
|
大姨妈是什么
|
探望病人买什么水果
|
农历六月十七是什么星座
|
什么是假性抑郁症
|
藏在我回忆里的那个人什么歌
|
子宫内膜厚是什么意思
|
类风湿性关节炎吃什么药
|
犬吠是什么意思
|
轻度强化是什么意思
|
nf是什么
|
玉的五行属性是什么
|
重睑术是什么意思
|
老年人适合喝什么茶
|
情人节送什么花
|
愚者是什么意思
|
大虾炒什么菜好吃
|
我国计划生育什么时候开始
|
脚怕冷是什么原因引起的
|
消防大队长是什么级别
|
外阴白斑挂什么科
|
你是什么星座
|
百度
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.
Blink: A rendering engine for the Chromium project
Wednesday, April 3, 2013
WebKit
is a lightweight yet powerful rendering engine that emerged out of
KHTML
in 2001. Its flexibility, performance and thoughtful design made it the obvious choice for Chromium's
rendering engine
back when we started. Thanks to the hard work by all in the community, WebKit has thrived and kept pace with the web platform’s growing capabilities since then.
However, Chromium uses a different
multi-process architecture
than other WebKit-based browsers, and supporting multiple architectures over the years has led to increasing complexity for both the WebKit and Chromium projects. This has slowed down the collective pace of innovation - so today, we are introducing
Blink
, a new open source rendering engine based on WebKit.
This was not an easy decision. We know that the introduction of a new rendering engine can have significant implications for the web. Nevertheless, we believe that having multiple rendering engines—similar to having multiple browsers—will spur innovation and over time improve the health of the entire open web ecosystem.
In the short term, Blink will bring little change for web developers. The bulk of the initial work will focus on internal architectural improvements and a simplification of the codebase. For example, we anticipate that we’ll be able to remove 7 build systems and delete more than 7,000 files—comprising more than 4.5 million lines—right off the bat. Over the long term a healthier codebase leads to more stability and fewer bugs.
Throughout this transition, we’ll collaborate closely with other browser vendors to move the web forward and preserve the compatibility that made it a successful ecosystem. In that spirit, we’ve set
strong guidelines for new features
that emphasize standards, interoperability, conformance testing and transparency.
To learn more about Blink visit our
project page
.
Posted by Adam Barth, Software Engineer
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
.
插队是什么意思
什么是肝炎
吃什么药怀孕最快
孩子急性肠胃炎吃什么药
湿疹是什么原因引起的
生活的意义是什么
万箭穿心代表什么生肖
过敏性荨麻疹吃什么药
wb是什么意思
子宫附件是什么意思
乙肝e抗体阴性是什么意思
骑马野战指什么生肖
阴道出血是什么原因
食禄痣是什么意思
网贷是什么
海参是补什么
glu是什么氨基酸
为什么会突然头晕
跳大神是什么意思
exr是什么牌子
梦见生娃娃是什么意思hcv9jop1ns9r.cn
火把节是什么节日hcv9jop6ns7r.cn
皮肤出现红点是什么原因hcv9jop0ns0r.cn
立冬吃什么liaochangning.com
公务员是干什么工作的hcv9jop3ns0r.cn
口腔义齿是什么hcv9jop3ns5r.cn
高危性行为是什么意思hcv9jop5ns9r.cn
苯醚甲环唑防治什么病hcv9jop4ns0r.cn
什么是礼仪hcv7jop9ns5r.cn
落下帷幕什么意思hcv7jop5ns2r.cn
花裤子配什么上衣hcv9jop4ns5r.cn
国家电网需要什么专业ff14chat.com
隔空打牛是什么意思hcv8jop9ns0r.cn
马蜂窝能治什么病hanqikai.com
午夜凶铃讲的是什么故事hcv7jop5ns6r.cn
脑梗吃什么药好hcv9jop6ns3r.cn
豆乳是什么ff14chat.com
贪慕虚荣是什么意思hkuteam.com
2月3日什么星座hcv9jop7ns5r.cn
牛黄安宫丸什么时候吃最好hcv8jop4ns5r.cn
百度
