You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the spec was first written, I assumed it was fine to say things like:
"Assign 0 to videoFrame.cropTop".
As well as
"Assign frameA.cropTop to frameB.cropTop"
I've learned that this isn't right. We should defined associated values or internal slots as backing for all attributes and assign/read from those instead of the attribute directly. The attribute should then be defined w/ getter steps that pull from the internal slot/value.
NOTE: This is not proposing any change to the exposed interfaces/attributes. Purely a spec wording detail.
The text was updated successfully, but these errors were encountered:
When the spec was first written, I assumed it was fine to say things like:
"Assign
0
tovideoFrame.cropTop
".As well as
"Assign
frameA.cropTop
toframeB.cropTop
"I've learned that this isn't right. We should defined associated values or internal slots as backing for all attributes and assign/read from those instead of the attribute directly. The attribute should then be defined w/ getter steps that pull from the internal slot/value.
NOTE: This is not proposing any change to the exposed interfaces/attributes. Purely a spec wording detail.
The text was updated successfully, but these errors were encountered: