# \[BUG-6587\] Perspective - editing multiple component props.styles overrides entire styles object **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [August 11, 2022, 5:01am UTC](https://forum.inductiveautomation.com/t/bug-6587-perspective-editing-multiple-component-props-styles-overrides-entire-styles-object/62901 "2022-08-11T05:01:18Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [September 13, 2022, 12:52am UTC](https://forum.inductiveautomation.com/t/bug-6587-perspective-editing-multiple-component-props-styles-overrides-entire-styles-object/62901/7 "2022-09-13T00:52:07Z")
Yeah, I can see your point, but I think an argument could be made either way. I think the problem with your idea is that it falls apart for the common case: _single_ component selection. Consider this: let’s say that the styles popup did a “merge” of the styles you’d selected in the UI and the styles that already existed on the selection. Now, you select a component that has a style, let’s say, it has margin set on it. You decide that instead of margin, you want padding. So you _remove_ margin in the UI and _add_ padding. Now you hit OK. The style editor does a “merge” of the style you’d designed and the existing object. Now you have margin _and_ padding on your style object. Pretty sure in that case you’d also be filing a bug report. --- _[View the full topic](https://forum.inductiveautomation.com/t/bug-6587-perspective-editing-multiple-component-props-styles-overrides-entire-styles-object/62901)._