Nikita Skovoroda

To reproduce: ```qml import QtQuick 2.0 Text { width: 100 height: 100 text: "foo" wrapMode: Text.WrapAnywhere // enum onWrapModeChanged: console.log('x' + wrapMode) } ``` `onWrapModeChanged` shouldn't fire here. This doesn't...

SystemPalette support for other OS

1

Atm, SystemPalette is populated only for macOS, on all the other platforms it just uses macOS colors. We probably need to support other systems, if possible. Btw, are macOS colors...

«QtQuick.Timer can roughly set short intervals» is flaky

3

I had to re-start several Travis CI tasks because of that lately. Perhaps we should increase the allowed marging again for now. /cc @henrikrudstrom

We should probably use getters/setters for properties there. Refs: #227, #226.

We should support user-supplied path preprocessors for `extractBasePath` and `readQmlDir`. Perhaps we could even bundle a set of such preprocessors for known providers, e.g. GitHub. This is a replacement for...

Once we sorted out the license question, we should add LibreJS support, as documented in https://www.gnu.org/software/librejs/free-your-javascript.html Our [MIT License](https://spdx.org/licenses/MIT), taken from SPDX, is also known as Expat license. People call...

Consider using browserify or webpack

13

Atm, we bundle `uglify-js` is `src` dir and have our own encapsulate wrappers. That is affecting several things and has to be fixed in some way, and using browserify or...

Benchmarks

1

To do the optimizations correctly, we need benchmarks first, or else we would be blindfolded. /cc @pavelvasev, @igosoft — you seem to be interested in performance =).

I mean the `.loadFile()` and `.loadQML()` methods. Targeting 1.0.0, as the API might change.

input event problems: FF behavior differs from Chromium and conflicts with what's documented on MDN

7

# Request type - [ ] Please close this issue, I accidentally submitted it without adding any details - [ ] New documentation - [x] Correction or update # Details...