You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose we amend the spec to allow for an additional option for $MESSAGE fields named "quotes_allowed", with a boolean value. We can then use this value in implementations to remove quotes or replace them with something else.
The text was updated successfully, but these errors were encountered:
I'd rather use javascript. There are lots of things that are filtered -- urls (sometimes), quotes (sometimes), it's all a bit fuzzy and tends to change a lot. I think the javascript command would make this easy, if you want to do it that way, and allows us to be more flexible.
Some members do not allow quotes in the message body, viewing it as a potential security risk for the form:
https://github.com/unitedstates/contact-congress/blob/master/members/S000320.yaml
I propose we amend the spec to allow for an additional option for $MESSAGE fields named "quotes_allowed", with a boolean value. We can then use this value in implementations to remove quotes or replace them with something else.
The text was updated successfully, but these errors were encountered: