Bug #2701
closedWCheckBox in Safari: changed- Event fired twice
0%
Description
A more detailed description of how this was discovered can be found here: http://redmine.webtoolkit.eu/boards/2/topics/8484?r=8523.
Abstract:
A function that is connected to the changed signal is observed to be entered twice after the user clicked on the WCheckBox.
Updated by Koen Deforche about 10 years ago
- Status changed from New to InProgress
- Assignee set to Roel Standaert
- Target version set to 3.3.2
Updated by Roel Standaert about 10 years ago
- Status changed from InProgress to Resolved
Hey,
The Safari workaround has become obsolete, causing the changed() event to be fired twice.
Regards,
Roel
Updated by I. Lazaridis about 10 years ago
I try to follow development a bit, and have a huge problem:
Issues are getting "Resolved", without any pointer to the relevant commit in the repo.
Is it possible to provide the links in future, thus following development will become easier.
(remember that this is somehow standard in open-source projects today)
Updated by Koen Deforche about 10 years ago
Hey,
Unfortunately, due to distributed nature of git, the 'repo' is actually not well defined. It's in our internal repo, but this only gets pushed to the external github repo after review.
Perhaps we can add a 'Status' state to differentiate between resolved-implemented, and resolved-available?
Regards,
koen
Updated by Koen Deforche about 10 years ago
- Status changed from Resolved to Closed