https://bugs.winehq.org/show_bug.cgi?id=32772
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek@codeweavers.com
--- Comment #21 from Jacek Caban jacek@codeweavers.com --- (In reply to Dmitry Timoshkov from comment #19)
Bug 49448 is clearly a bug in Gecko (despite its component is set to mshtml).
Oh, right, this would be another one with current definition. But if we changed the definition as Anastasius suggested, it would fit mshtml. One way to look at Wine Gecko is that it's an internal (but significant) implementation detail of mshtml and as such bugs belong there. The fact that the code that needs to be changed is in Gecko may be expressed in a summary.
In fact, it has always been partially this way, the separated product was meant as a tool to properly track status. For bugs that require Gecko changes, we can resolve them in gecko product as soon as it they are fixed in Wine Gecko git and later move resolved bug to mshtml component when Wine is upgraded to use the fixed version of Gecko. By retiring separated product we lose the ability to have 'fixed in Wine Gecko git, but not yet in Wine' state. The volume of such bugs is low enough that I don't mind.
And to be fair, it's usually more than two bugs that belong to gecko product under current definitions. The fact that there are no more bugs is partially because I recently released Gecko update that fixed a few of them. There is still quite a bit of work that would be nice to have done on Gecko side. It's just that majority of remaining mshtml work is in Wine part of mshtml using the existing Gecko (that is no longer updated every few months with tons of new features and problems merged from upstream).