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
(Leaving this issue here just so I don't forget about it over the weekend.)
While troubleshooting an issue trying to bypass the automatic webp formatting with @smccafferty, we noted that none of the expected formats (?webp=false, ?webp=0, ?webp=no) for setting the webp query argument to false worked as we'd expected. I guess this makes sense, because URL query parameters are interpreted as strings both by the URLSearchParameters() js API and by AWS Lambda's queryStringParams. But it was surprising that 'false', '0', and 'no' all evaluated as true.
Sean was able to work out that setting the attribute to an empty string, like ?webp=, works for disabling webp. But I'd like to see a more intuitive interface.
The text was updated successfully, but these errors were encountered:
(Leaving this issue here just so I don't forget about it over the weekend.)
While troubleshooting an issue trying to bypass the automatic webp formatting with @smccafferty, we noted that none of the expected formats (
?webp=false
,?webp=0
,?webp=no
) for setting thewebp
query argument to false worked as we'd expected. I guess this makes sense, because URL query parameters are interpreted as strings both by theURLSearchParameters()
js API and by AWS Lambda'squeryStringParams
. But it was surprising that 'false', '0', and 'no' all evaluated as true.Sean was able to work out that setting the attribute to an empty string, like
?webp=
, works for disabling webp. But I'd like to see a more intuitive interface.The text was updated successfully, but these errors were encountered: