The Kroger Feedback Survey is a platform for customers to share their shopping experiences and provide feedback on product availability and customer service. By visiting https://kroger-feedback.page/ and entering receipt details, shoppers can contribute to improving services and have the opportunity to win rewards. This simple process allows individuals to make their voices heard and play a part in enhancing overall shopping experiences at Kroger. Whether it's positive feedback or suggestions for improvement, the survey is a valuable tool for customers.

What is incomprehensible right currently is prototyping dropdown select construction parts. I can't get settled parts to target root part states. So one can display a dropdown and rollover submenu, but when you settle on a decision it won't change the construction part text since that part is in the root. https://teststripbank.com/shop/

What is inconceivable right now is prototyping dropdown select structure components. I cannot get settled parts to target root part states. So one can model a dropdown and rollover submenu, however when you make a choice it will not change the structure component text since that component is in the root. https://condolobby.com/condos-in-mississauga/

What is impossible at the moment is prototyping dropdown select form elements. I cant get nested components to target root component states. So one can prototype a dropdown and rollover submenu, but as soon as you make a selection it won't change the form element text because that element is in the root.

I figured out a way to do it myself. Create a radio button component with a on/off state. Then create a rectangle for each button in the group and cover the radio button with the rectangle. Third, create a component that includes the label, radio buttons, and rectangles. Next, create a state for each option. Lastly, go to prototype and trigger the rectangles on tap to go to the state for each option. Once finished with triggering each rectangle, change the transparency to 0%. It's best group each option with each rectangle and have them separate from each other until after you're done triggering. Grouping each will help with any stacking you may choose to do.

how is this not yet implemented? how many programmers are working for XD?

Exactly, this is preventing us to switch fully to XD from Axure. It's really basic for prototyping common interactions.

I agree, just like Axure. Strange that this is still under review

to Mundstrøm you can do this now but use components inside another component. Problem is you have to mark in all states all actions for all "radios"! If you want component to activate parent component state add it to group and give action to group, just don't make same actions as component inside.

At least let us build radio button groups where changing the state of one to "on" switched the state of he others to "off" or even better a special type of group where "if a component in this group's state is changed to (name of state) then switch other components in this group to state (name of state) - this limitation makes me pull my hair out EVERY TIME I use XD.

Also for example : lets a modal opens up and asks for info on a text area - user should hv the ability to access the value what was entered in the modal on other pages or artboard :p

a plugin which will let us add form input fields would be amazing - like dropdowns - input text - and different components and also set styles to these form inputs

Could be animated in XD right now.

Isn't this functionality that component states already provide??

For drop downs, I have to write down the wording of each drop down item on the side of the art board.

Drop downs, radio buttons, or any form elements feel pretty fundamental.

We NEED Radio Buttons, checkboxes, and DROP MENUS that we use to can build interactive forms - allowing users to move to other artboards.

Otherwise, the spiderweb maze of artboards gets REDICULOUS!!!

we need radio buttons, checkboxes, text fields, DROPDOWN MENUS asap.. it takes STUPID long to create these

Please add this! This would shoot most of the competition out of the water for creating high fidelity prototypes.

Yes please please! Just need to have the most basic form components like text, checkbox, radio, popup. I think that would cover 90%+ and allow this app to go to the next level. Please add some interactive form components, please :)

I think this could be solved by the new component states options if an extra option is added. We need a way to set/define a "UI group" to any component(s) in a given artboard. For "radio buttons" there could be a "single state mode" that sets all other components in that group to their default state if any one of them is is clicked.