Test fragment scrolling and history restoration interaction w/ scroll anchoring.

third_party/WebKit/Source/build/scripts/templates/InternalRuntimeFlags.idl.tmpl

Index: third_party/WebKit/Source/build/scripts/templates/InternalRuntimeFlags.idl.tmpl
diff --git a/third_party/WebKit/Source/build/scripts/templates/InternalRuntimeFlags.idl.tmpl b/third_party/WebKit/Source/build/scripts/templates/InternalRuntimeFlags.idl.tmpl
index cfdd2c0d057bb5a66446f65b52a0ef0b1421cd29..16e4693ea7fd77427af2fa39fcba3c0bcf5f734b 100644
--- a/third_party/WebKit/Source/build/scripts/templates/InternalRuntimeFlags.idl.tmpl
+++ b/third_party/WebKit/Source/build/scripts/templates/InternalRuntimeFlags.idl.tmpl
@@ -5,11 +5,11 @@
     GarbageCollected,
 ] interface InternalRuntimeFlags {
     {% for feature in standard_features %}
-{#
-    Currently assuming that runtime flags cannot be changed after startup
-    it's possible that some can be and should be conditionally readonly.
-#}
     {%+ if feature.condition %}[Conditional={{feature.condition}}] {% endif -%}
+    {% if feature.settable_from_internals %}
+    attribute boolean {{feature.first_lowered_name}}Enabled;

[jbroman, 2016/04/28 14:24:39]

Mind a comment somewhere (maybe here?) clarifying that these are indeed reset
between layout tests? It took some digging for me to convince myself that this
was safe, since the place where it's reset isn't obvious.

[ymalik, 2016/04/28 15:05:06]

Yes. Added to cpp.tmpl.

+    {% else %}
     readonly attribute boolean {{feature.first_lowered_name}}Enabled;
+    {% endif %}
     {% endfor %}
 };