Unexpected Outcome in Parsing Component Attributes from HTML

Description:
I noticed that the parsing of component attributes has an unexpected outcome when the last schema data attribute being set is a string and followed by a lone component attribute.

The below example results in the log component's data.channel to be assigned 'grabbable'.

<a-entity log="max:10;channel:main"   grabbable    geometry="primitive: plane" 
    position="-9.25 2 -11.2" rotation="0 90 0" scale="2 2 2" 
    material="color: #153D0F; side:double" text="color: #CEA579">
</a-entity>

The below example results in the log component's data.channel to be assigned 'main'.

<a-entity grabbable    log="max:10;channel:main"   geometry="primitive: plane" 
     position="-9.25 2 -11.2" rotation="0 90 0" scale="2 2 2" 
     material="color: #153D0F; side:double" text="color: #CEA579">
</a-entity>

• A-Frame Version: v0.9.2
• Platform / Device: MacOS Chrome Browser

Start at the component-attribute parsing entry point described by the reproducer and compare parsing when the lone grabbable attribute appears before versus after log. Reproduce the HTML examples in a focused test or existing parser coverage, then verify that log.data.channel remains "main" in both orders.