Open pbowen-oc opened 4 years ago
Possible explanation:
<sub>, <sup>, <span>
might (sort of accidentally) on non-touchscreen devices - not in html: https://codepen.io/MartijnR/pen/OJJeLaPhttps://docs.google.com/spreadsheets/d/1CVS4pwhcTMma9EKhkTyxl5veDK0gf3BhjyFhg-EZBcw/edit?usp=sharing
http://localhost:8005/::8nXsmspg
http://localhost:8005/::8nXsmspg?touch=true (mobile simulation)
desktop | mobile | |
---|---|---|
regular radiobutton/checkbox select - internal data | :x: | ❌ |
regular radiobutton/checkbox select - external data | :x: | ❌ |
pulldown select - internal data | html only (accidental) | :x: |
pulldown select - external data | html only (accidental) | :x: |
"internal data" means the data is part of the XForm definition (there are actually two kinds, but not really necessary to make that distinction).
@pbowen-oc current situation is as above. Theoretically it would be fairly easy to support markdown (incl html) for regular radiobutton/checkbox selects from internal data. The reason it isn't done is to avoid confusing users. It's hard to explain why some work and others don't. I had expected the above table to have only ❌. Any support is accidental.
To get support for all regular radiobuttons/checkboxes means we have to move markdown parsing to the client (it is now happening during transformation). This will probably noticeable slow down form loading.
For pulldowns I don't see a good way to get support on mobile devices, so I regret the accidental support very much, and would prefer to remove that.
Using the tags in choice labels seems to be working with "minimal" appearance but not with appearances that show radio buttons. The expectation is that it will work for both.
Dropdown:![Bug2](https://user-images.githubusercontent.com/25179620/68343634-3f5a7a80-00bb-11ea-9b5a-3379da91e93a.PNG)
Radio Button:![Bug1](https://user-images.githubusercontent.com/25179620/68343638-41243e00-00bb-11ea-963e-42e8eae56618.PNG)
Note that those screenshots are from a theme-grid form.