Deprecate / remove align-model attribute
See original GitHub issueIn #441 , we introduced the align-model
attribute as an escape-hatch for users who want to stage their models in a special way and did not want to use the default staging.
Once we implement #453 , align-model
won’t be as useful, and the escape hatch use case will mostly be covered by camera-target
. At that point, we should deprecate and remove align-model
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Align Attribute Deprecated - html - Stack Overflow
On a site I'm working with we are using the latest doctype (). Should I try my best not to use the align...
Read more >Deprecated HTML attributes - Strict Quirks
A list of HTML attributes which have been deprecated, and the features with which they should be replaced. ; ALIGN in table, float...
Read more >Deprecated HTML Attributes - W3docs
Attributes Description Deprecated in
align Specifies the alignment of the element, , , , , ‑,
background Specifies the background image
bgcolor Specifies the background color,...
Read more >Deprecate/Private/Fork/Rename model changes Proposal
After another discussion with Ran, we want to align all "metadata" types we have on the component. Instead of having componentMetadata property on...
Read more >What Replaced Td Align After HTML5?: We've Got The ...
Attributes for ALIGN = LEFT | CENTER | MIDDLE | RIGHT VALIGN = TOP ... This deprecated attribute was once used to center...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
deprecated on 0.6, removal now slated for 0.7.
We should also think about this in the context of #426.