mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
96b58d1f07
This patch fixes a regression from https://hg.mozilla.org/mozilla-central/rev/31695984cfe2 (bug 1025709). That patch replaced the EnsureStyleRuleFor method on ElementTransitions and ElementAnimations with a common method in CommonElementAnimationData. ElementTransitions::EnsureStyleRuleFor would create a new style rule if there was no style rule (mStyleRule == nullptr) or if the refresh time was old (mStyleRuleRefreshTime != aRefreshTime). ElementAnimations::EnsureStyleRuleFor, however, would create a new style rule only if mStyleRuleRefreshTime was null or old since a null style rule may still be valid for animations (unlike transitions). If we bail as soon as we a null style rule we would never update mNeedsRefreshes when the animation finishes. The unified version of EnsureStyleRuleFor in CommonElementAnimationData adopted the behavior from ElementAnimations checking for a null or old mStyleRuleRefreshTime. However, nsTransitionManager::StyleContextChanged sets mStyleRule to nullptr to indicate that we need to generate a new style rule. This means that we will fail to create a style rule for the transition in some cases. This patch addresses this by making nsTransitionManager::StyleContextChanged set mStyleRuleRefreshTime to a null timestamp. Setting mStyleRule to nullptr is no longer necessary since EnsureStyleRuleFor will do this when necessary and nsTransitionManager::mStyleRule is only used after calling EnsureStyleRuleFor. |
||
|---|---|---|
| accessible | ||
| addon-sdk | ||
| b2g | ||
| browser | ||
| build | ||
| caps | ||
| chrome | ||
| config | ||
| content | ||
| db/sqlite3 | ||
| docshell | ||
| dom | ||
| editor | ||
| embedding | ||
| extensions | ||
| gfx | ||
| hal | ||
| image | ||
| intl | ||
| ipc | ||
| js | ||
| layout | ||
| media | ||
| memory | ||
| mfbt | ||
| mobile | ||
| modules | ||
| mozglue | ||
| netwerk | ||
| nsprpub | ||
| other-licenses | ||
| parser | ||
| probes | ||
| profile | ||
| python | ||
| rdf | ||
| security | ||
| services | ||
| startupcache | ||
| storage | ||
| testing | ||
| toolkit | ||
| tools | ||
| uriloader | ||
| view | ||
| webapprt | ||
| widget | ||
| xpcom | ||
| xpfe | ||
| xulrunner | ||
| .clang-format | ||
| .clang-format-ignore | ||
| .gdbinit | ||
| .gitignore | ||
| .hgignore | ||
| .hgtags | ||
| .lldbinit | ||
| .lock | ||
| .reviewboardrc | ||
| aclocal.m4 | ||
| Android.mk | ||
| AUTHORS | ||
| client.mk | ||
| client.py | ||
| CLOBBER | ||
| configure.in | ||
| LEGAL | ||
| LICENSE | ||
| mach | ||
| Makefile.in | ||
| moz.build | ||
| mozilla-config.h.in | ||
| README.txt | ||
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
http://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
http://developer.mozilla.org/en/docs/Creating_a_patch
http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on http://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/
- or -
http://nightly.mozilla.org/