UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10032.86.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.140 Safari/537.36

Steps to reproduce the problem:
1. Open https://examples.x3dom.org/example/x3dom_jQueryManip.xhtml
2. Inspect the elements, find the <Transform> element
3. In the inspector, try setting the attribute `translation` to `translation="0,5,0"` (observe nothing happens)
4. Then try using `$0.setAttribute('translation' '0,5,0')` in the console instead (observe that it works)

What is the expected behavior?
When modifying the attribute in the inspector's HTML view, it should work just like using $0.setAttribute does.

What went wrong?
It doesn't work.

Did this work before? N/A 

Chrome version: 63.0.3239.140  Channel: n/a
OS Version: 10032.86.0
Flash Version: 

This leads me to make a hypothesis that maybe Chrome isn't using `getAttribute` or `setAttribute` for showing and for allowing modification of the element attributes, respectively.

If this is the case, it'd be nice to use these APIs rather than accessing HTML engine internals, because nowadays it is possible for Custom Element authors to override {set,get}Attribute to do certain things, so bypassing these by reaching into the internals of the engine would cause certain things not to work right when people try modifying elements through the inspector.

Is this the case, that devtools sets/gets attributes in some other way? If so, in what way does it set and get attributes?