Support for Shadow DOM and Pointer Lock

[Benvie]

These are just toggles in chrome:flags but I can't figure out how to enable them in CEF. Pointer lock provides an app for doing mouse capture on DOM elements from JS which is really useful for doing something like a custom title bar. Shadow DOM allows creation of custom elements which is useful for providing JS GUI apis to users.

[Benvie]

I was able to find out where to at least force enable these in Chrome.

third_party/WebKit/Source/WebCore/bindings/generic/RuntimeEnabledFeatures.cpp

In there you can modify various flags. Most or all of these are already compiled into Chromium, they are simply disabled by default. I changed the following from false to true with success:
bool RuntimeEnabledFeatures::isShadowDOMEnabled = true;
bool RuntimeEnabledFeatures::isStyleScopedEnabled = true;
bool RuntimeEnabledFeatures::isPointerLockEnabled = true;
bool RuntimeEnabledFeatures::isMediaSourceEnabled = true;
bool RuntimeEnabledFeatures::isInputTypeDateEnabled = true;

[fddima]

And how it is can be used? May be you have links?

[custa1200]

And how it is can be used? May be you have links?

Shadow DOM is part of Web Components

http://dvcs.w3.org/hg/webcomponents/raw ... index.html

[fddima]

Thanks. As for me, it is looks as CEF require this settings too.
Components looks promising.

[custa1200]

Thanks. As for me, it is looks as CEF require this settings too.
Components looks promising.

Components are shaping up to be awesome. Also really need scoped variables for them to work too, so that setting also needs to be switched.

[magreenblatt]

Please add an issue to the CEF issue tracker for enabling these features.

[fddima]

Please add an issue to the CEF issue tracker for enabling these features.

Issue 689 added.