During T288498: Update less.php port to support Less.js 3.13 behaviours, we have learned that previous Less.php maintainers did not accurately check-in or pass the Less.js 2.5.3 specifications. We have learned that a number of suble behaviour differences and missing features have gone unnoticed as a result. This is a tracking task to make sure any unintentional/undocumented differences are resolved, and documented differences reduced to a minimum (i.e. by design we don't allow insecure code evaluation, but anything else can presumably be kept in sync for parity and portability).
Plan:
- Check in full test suite.
- Create tasks for test failures, and temporarily disable these with reference to the task.
- Work through the tasks, with intermittent releases to reduce risk, invite feedback, and discover regressions early.