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

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

+{% from "macros.tmpl" import license %}
+{{ license() }}
+
+#include "InternalRuntimeFlags.h"
+
+namespace blink {
+
+InternalRuntimeFlags* InternalRuntimeFlags::create()
+{
+    return new InternalRuntimeFlags;
+}
+
+InternalRuntimeFlags::InternalRuntimeFlags()
+    : m_{{standard_features[0].first_lowered_name}}(RuntimeEnabledFeatures::{{standard_features[0].first_lowered_name}}Enabled())

[wkorman, 2016/04/26 19:01:18]

Might be better to do this as a straight for-loop and conditionally pre-pend a
comma. But I realize pragmatically we always have at least one. Would make code
more concise, but generated code less readable. Thoughts?

[ymalik, 2016/04/26 20:17:39]

Yeah. We're also doing it that way in the template for RuntimeEnabledFeatures,
so I guess it would also be more consistent.

https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit...

+    {% for feature in standard_features[1:] %}
+    , m_{{feature.first_lowered_name}}(RuntimeEnabledFeatures::{{feature.first_lowered_name}}Enabled())
+    {% endfor %}
+{
+}
+
+{% for feature in standard_features %}
+{% if feature.set_from_internals %}
+void InternalRuntimeFlags::set{{feature.name}}Enabled(bool isEnabled)
+{
+    RuntimeEnabledFeatures::set{{feature.name}}Enabled(isEnabled);
+}
+{% endif %}
+{% endfor %}
+
+{% for feature in standard_features %}
+bool InternalRuntimeFlags::{{feature.first_lowered_name}}Enabled()
+{
+    return RuntimeEnabledFeatures::{{feature.first_lowered_name}}Enabled();
+}
+{% endfor %}
+
+} // namespace blink