<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[200082] trunk/Websites/webkit.org</title>
</head>
<body>
<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; }
#msg dl a { font-weight: bold}
#msg dl a:link { color:#fc3; }
#msg dl a:active { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<dl class="meta">
<dt>Revision</dt> <dd><a href="http://trac.webkit.org/projects/webkit/changeset/200082">200082</a></dd>
<dt>Author</dt> <dd>timothy@apple.com</dd>
<dt>Date</dt> <dd>2016-04-26 06:52:15 -0700 (Tue, 26 Apr 2016)</dd>
</dl>
<h3>Log Message</h3>
<pre>Remove hard-wraps from the feature policy markdown so it renders full width on the site.
* feature-policy.md:</pre>
<h3>Modified Paths</h3>
<ul>
<li><a href="#trunkWebsiteswebkitorgChangeLog">trunk/Websites/webkit.org/ChangeLog</a></li>
<li><a href="#trunkWebsiteswebkitorgfeaturepolicymd">trunk/Websites/webkit.org/feature-policy.md</a></li>
</ul>
</div>
<div id="patch">
<h3>Diff</h3>
<a id="trunkWebsiteswebkitorgChangeLog"></a>
<div class="modfile"><h4>Modified: trunk/Websites/webkit.org/ChangeLog (200081 => 200082)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/Websites/webkit.org/ChangeLog 2016-04-26 13:32:57 UTC (rev 200081)
+++ trunk/Websites/webkit.org/ChangeLog 2016-04-26 13:52:15 UTC (rev 200082)
</span><span class="lines">@@ -1,3 +1,9 @@
</span><ins>+2016-04-26 Timothy Hatcher <timothy@apple.com>
+
+ Remove hard-wraps from the feature policy markdown so it renders full width on the site.
+
+ * feature-policy.md:
+
</ins><span class="cx"> 2016-04-14 Edward O'Connor <eoconnor@apple.com>
</span><span class="cx">
</span><span class="cx"> Publish the Web-exposed feature policy on webkit.org.
</span></span></pre></div>
<a id="trunkWebsiteswebkitorgfeaturepolicymd"></a>
<div class="modfile"><h4>Modified: trunk/Websites/webkit.org/feature-policy.md (200081 => 200082)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/Websites/webkit.org/feature-policy.md 2016-04-26 13:32:57 UTC (rev 200081)
+++ trunk/Websites/webkit.org/feature-policy.md 2016-04-26 13:52:15 UTC (rev 200082)
</span><span class="lines">@@ -1,28 +1,14 @@
</span><span class="cx"> ### Runtime flags
</span><span class="cx">
</span><del>-Generally, new author-facing features should be implemented behind
-**runtime flags**. Initially, such flags should be disabled on trunk. As
-work on a feature matures, its flag may be enabled on trunk. Eventually,
-runtime flags guarding widely deployed, stable features should be
-removed.
</del><ins>+Generally, new author-facing features should be implemented behind **runtime flags**. Initially, such flags should be disabled on trunk. As work on a feature matures, its flag may be enabled on trunk. Eventually, runtime flags guarding widely deployed, stable features should be removed.
</ins><span class="cx">
</span><del>-The following criteria define when runtime flags should be enabled or
-disabled **on trunk**. This policy is not intended to embody or
-communicate a feature release policy for any particular WebKit port or
-product which embeds WebKit. It is the responsibility of each port to
-determine if or when runtime flags should be enabled or disabled for
-release. Ports are encouraged to document any additional criteria they
-may use.
</del><ins>+The following criteria define when runtime flags should be enabled or disabled **on trunk**. This policy is not intended to embody or communicate a feature release policy for any particular WebKit port or product which embeds WebKit. It is the responsibility of each port to determine if or when runtime flags should be enabled or disabled for release. Ports are encouraged to document any additional criteria they may use.
</ins><span class="cx">
</span><del>-In some cases, compile time flags should be used in addition to or
-instead of runtime flags:
</del><ins>+In some cases, compile time flags should be used in addition to or instead of runtime flags:
</ins><span class="cx">
</span><del>-* When merely compiling a feature in significantly impacts the
- hackability or livability of trunk.
-* When a feature requires a platform-specific backend that is not
- available on all platforms.
-* When some ports or platforms have resource constraints which require
- the ability to remove the feature completely from builds.
</del><ins>+* When merely compiling a feature in significantly impacts the hackability or livability of trunk.
+* When a feature requires a platform-specific backend that is not available on all platforms.
+* When some ports or platforms have resource constraints which require the ability to remove the feature completely from builds.
</ins><span class="cx"> * When a feature is otherwise only relevant to some ports or platforms.
</span><span class="cx">
</span><span class="cx"> That said, runtime flags are preferred whenever feasible.
</span><span class="lines">@@ -31,33 +17,23 @@
</span><span class="cx">
</span><span class="cx"> * When work on the feature begins.
</span><span class="cx"> * When the feature is not intended to be Web-exposed.
</span><del>-* When the feature is defined in a Web standard which is immature or is
- likely to incompatibly change.
-* If enabling the feature would negatively affect the livability of
- trunk. (In such cases a compile-time flag may also be warranted.)
</del><ins>+* When the feature is defined in a Web standard which is immature or is likely to incompatibly change.
+* If enabling the feature would negatively affect the livability of trunk. (In such cases a compile-time flag may also be warranted.)
</ins><span class="cx">
</span><span class="cx"> Later, a runtime flag may be **enabled on trunk**:
</span><span class="cx">
</span><del>-* When the feature is defined in a mature Web standard which is
- unlikely to incompatibly change.
-* If the implementation of the feature is relatively mature and it is
- ready for wider testing or review.
</del><ins>+* When the feature is defined in a mature Web standard which is unlikely to incompatibly change.
+* If the implementation of the feature is relatively mature and it is ready for wider testing or review.
</ins><span class="cx"> * If support for the feature is required for Web compatibility.
</span><span class="cx">
</span><del>-Eventually, a runtime flag may be removed and the feature made **always
-on**:
</del><ins>+Eventually, a runtime flag may be removed and the feature made **always on**:
</ins><span class="cx">
</span><del>-* When most or all major ports of WebKit are shipping the feature and
- none plan to turn it off.
</del><ins>+* When most or all major ports of WebKit are shipping the feature and none plan to turn it off.
</ins><span class="cx">
</span><span class="cx"> ### Naming
</span><span class="cx">
</span><span class="cx"> In general, new features **should not be prefixed**.
</span><span class="cx">
</span><del>-A new feature **should be prefixed** if the feature is not intended to
-be Web-exposed. (And, as established in the previous section, such
-a feature's runtime flag should be disabled on trunk.)
</del><ins>+A new feature **should be prefixed** if the feature is not intended to be Web-exposed. (And, as established in the previous section, such a feature's runtime flag should be disabled on trunk.)
</ins><span class="cx">
</span><del>-A prefix specific to the product or content type is preferred over the
-`-webkit-` prefix. For example, a feature intended for FooCorp's
-flagship Foo product should get a `-foo-` prefix, not a `-webkit-` one.
</del><ins>+A prefix specific to the product or content type is preferred over the `-webkit-` prefix. For example, a feature intended for FooCorp's flagship Foo product should get a `-foo-` prefix, not a `-webkit-` one.
</ins></span></pre>
</div>
</div>
</body>
</html>