Daniel
To backup my claim, #16 laid out some very clear arguments for an addition to the 1.2 draft, and #17 created the appropriate EBNF changes. I no longer work with...
Could privacy badger not inject its own script hashes into the CSP header to solve this?
I am not able to reproduce on Chrome, but I also wouldn't consider this a bug in Firefox. In this case, Firefox is doing exactly what I am telling it...
It would be awesome if @scotthelme would weigh on in the best way to resolve this issue. Clearly Privacy Badger is a major cause of CSPs being reported. Is injection...
Yeah, this one looks like a major false positive. I wonder how it got added in the first place. Just FYI, this project is kinda in limbo at the moment....
Looks fine to me: ```json [{"":"m","singular":"f","plural":"n"},{"":"infinitive","singular":"być","plural":"być"},{"":"1st","singular":"jestem,\n -m","plural":"jestem,\n -m"},{"":"2nd","singular":"jesteś, -ś","plural":"jesteś, -ś"},{"":"3rd","singular":"jest","plural":"jest"},{"":"1st","singular":"byłem","plural":"byłam"},{"":"2nd","singular":"byłeś","plural":"byłaś"},{"":"3rd","singular":"był","plural":"była"},{"":"1st","singular":"będę","plural":"będę"},{"":"2nd","singular":"będziesz","plural":"będziesz"},{"":"3rd","singular":"będzie","plural":"będzie"},{"":"1st","singular":"byłbym","plural":"byłabym"},{"":"2nd","singular":"byłbyś","plural":"byłabyś"},{"":"3rd","singular":"byłby","plural":"byłaby"},{"":"1st","singular":"niech będę","plural":"niech będę"},{"":"2nd","singular":"bądź","plural":"bądź"},{"":"3rd","singular":"niech będzie","plural":"niech będzie"},{"":"active adjectival participle","singular":"będący","plural":"będąca"},{"":"contemporary adverbial participle","singular":"będąc","plural":"będąc"},{"":"anterior adverbial participle","singular":"bywszy","plural":"bywszy"},{"":"verbal noun","singular":"bycie","plural":"bycie"}] ``` The template does this: ``` var table =...
I just looked at the HTML more closely @onsa - I don't think this tool can work with this type of table. There are way too many `` spread throughout...
Any thoughts on this PR?
Just checking in that the issue continues with version `2019.6.0`
This is not a feature that is supported, you will have to cast the values yourself