This will help us bridge a UX issue in QuestionElement but also in the larger HAX schema. If you have a slot / flexible content area, we'll inject the <p> or whatever tag w/ slot set appropriately and then you edit in the page. This is weird though becasue for the rest of the element you edit in the properties / settings area.
But... what if the slot isn't there / is option as is the case w/ QuestionElement. Well, you have a button on the side for Edit Guess which when hitting that, ensures that slot exists and focuses the content in question. This may end up needing a add guess vs edit guess and remove guess connotation where the wiring is aware of the slots and reacts to their existence (as is the case in that element too w/ the hasGuess logic applied initially so we know what containers to render.
This will help us bridge a UX issue in QuestionElement but also in the larger HAX schema. If you have a slot / flexible content area, we'll inject the
<p>or whatever tag w/ slot set appropriately and then you edit in the page. This is weird though becasue for the rest of the element you edit in the properties / settings area.But... what if the slot isn't there / is option as is the case w/ QuestionElement. Well, you have a button on the side for
Edit Guesswhich when hitting that, ensures that slot exists and focuses the content in question. This may end up needing aadd guessvsedit guessandremove guessconnotation where the wiring is aware of the slots and reacts to their existence (as is the case in that element too w/ thehasGuesslogic applied initially so we know what containers to render.