Skip to main content
jenlpro
jenlpro
Helper ⭐️
May 4, 2023

Lock C360 field position in place regardless of Zoom level/window size

  • May 4, 2023
  • 3 replies
  • 60 views

This is something I find really overwhelmingly frustrating, but I position fields in my attributes boxes on the C360 so that they appear in a specific order. However, when I work on my laptop, I keep my window zoomed out to 70%-80% and everything changes position, making it harder to use & less intuitive in terms of the flow of the fields.

I’d love it if fields would lock into place on page layouts, regardless of the zoom/window size (within reason - thinking how in Salesforce for example you have 2 columns to populate fields or so and they stay in-place until your window is ½ size or so)

    3 replies

    alizee
    alizee
    VIP ⭐️⭐️⭐️⭐️⭐️
    May 5, 2023

    Is that an ask for the frontend (i.e. what end users see) or what you see when you move/build things @jenlpro ?

    The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
    jenlpro
    jenlproAuthor
    Helper ⭐️
    May 5, 2023

    @alizee I would say it’s both … make it more structured on the admin side so that the end-users see what we configure. I feel like right now, it’s disjointed - I can drag fields into the 1st, 2nd, and 3rd space in the same row for an attributes box, for example, and then save the configuration… but when the end-user is looking at it, depending on their window size or their zoom level, it will move into different positions and cause boxes that were configured to sit side-by-side to stack, as well as make an attribute section that should have all fields visible on the layout require scrolling to see fields 😣

    alizee
    alizee
    VIP ⭐️⭐️⭐️⭐️⭐️
    May 9, 2023

    By essence that’s how a responsive screen behaves, and locking widgets (or attributes) into place would defeat the purpose of a responsive screen. Not sure we can’t C360 not to be responsive (I certainly don’t).  

    What might be best would be to formalize/clarify how the items flow from one row to another or to a column so we understand how to lay them out (and there’s certainly a bit more logic to be brought into how they flow as it does indeed seem a bit random). 

    The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
    Terms & ConditionsAccessibility statement