When viewing SFMs on the Browser that have an unsupported literal mapped as part of them then they fail with an error message. This idea is to request that the doesn't happen but instead the mapping line for the literal is ignored if the literal is not recognised.
Examples are the three new literal for Latitude, longitude and accuracy.
We would not want to maintain two different versions of each SFM that uses these literals but would just want them to be ignored when on the browser.
What is the underlying problem do you intend to solve with this idea?
Error message shown when literal is unsupported
How is the problem being addressed today, if at all?