Aidan Woods
Aidan Woods
Issue to track whether we want Parsedown to be able to tell when it should continue a block or start a new one based on precedence. This is a separate...
2.0.0
Big PR to track everything for planned changes towards 2.0.0—please leave reviews here (preferably by adding a review to the relevant code site), or make PRs targeting the `2.0.x` branch...
A different take on headerless tables where syntax omits the header instead of leaving it empty – inspired by #538. --- ~~This also includes a bugfix commit to permit single...
It would be perhaps useful if Parsedown could output information useful for debugging (i.e. version, enabled options/settings, extensions in use, or the equivalent set of things as per the next...
2.0.0
Corresponding PR to https://github.com/erusev/parsedown/pull/708
Moving this issue from: https://github.com/erusev/parsedown/issues/616 --- Quoting @oufloued: > had this problem with abbreviation definition ending with czech characters. > ( which are quite common in czech republic ;) anyway...
As alluded to in #32, keys should to be strongly bound to their parameter choices to prevent algorithm confusion attacks (so byte arrays or similar shouldn't be accepted). From the...
[HPKP is dead](https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/he9tr7p3rZ8/eNMwKPmUBAAJ). Okay, well not quite yet 😉, but the end looks to be nigh unless something changes to fix it. [HPKP](https://tools.ietf.org/html/rfc7469) was a standard developed in hope of...
In future versions we should rework how [cookie upgrades](https://github.com/aidantwoods/SecureHeaders/blob/master/docs/v2/protectedCookie.md) are handled. Sites which care about security related headers being reliably delivered should already be using HTTPS on all their pages...
As hinted in https://github.com/aidantwoods/SecureHeaders/pull/67#issuecomment-345561882, the public API could do with some better coverage.