While I think that's a good general guideline for us to work to, I don't think it's something we can guarantee for reasons that have been expressed to you before. > vtable indices for dot security releases. > my general proposal is *not* to make any changes that change existing function We are still considering it, but we would like to be able to ship this release sooner rather than later. To do this would add a week to our shipping schedule. > so that RF does not crash and we have time to get rid of offending calls. > can you just keep the order of calls in FF 3.0.2,
#Roboform not working in firefox update#
Or you can update RoboForm to not break, I guess, but then when we take this patch for 3.0.3, the vtable will go back to how it was before 3.0.2 :( We *will* take Roc's patch for Firefox 3.0.3, at which point RoboForm should work again. I am saying that at this point we are unwilling to delay the release of Firefox 3.0.2 any further, so we will likely be following option #2. Ship Firefox 3.0.2 tomorrow and blocklist the version of RoboForm that crashes. Delay the release of Firefox 3.0.2, take this patch & rebuild.Ģ. > then FF 3.0.3 will work ok with RoboForm?ġ. > do you say FF 3.0.2 will crash or block RF and Vadim: sorry, didn't mean to confuse you. These are public interfaces that shouldn't change in security releases, although they may change between major releases. > *nsIDOMCSS2Properties used to work with CSS > *nsIDOMDocumentXBL used to receive XUL elements (But unlike the previous case, nsIWidget is not potentially public.) Same comment as above about more information being needed. > Roboform requires info about Firefox windows.
#Roboform not working in firefox windows#
> *nsIWidget to get handles of firefox windows (for example requires for Basic
The frozen DOM event APIs should let you do this. > *nsIMutationObserver to catch DOM tree mutation events You'd need to provide more information about what it is you actually want to do here (although maybe somebody else knows of frozen interfaces for this, or is willing to say that this interface shouldn't change for security releases, which might be the case) - and this bug report probably isn't the best place. > *nsIDocShellTreeItem used to search for HTML docshells (Public interfaces that shouldn't change for security releases, but might change for major releases - in fact, the two interfaces I pointed you to will be combined in the next major release.) See comment 12 for public interfaces to do this. > *nsIFrame to get html element frame (to get element coordinates) > Examples of using unfrozen interfaces in Roboform: HWND hwnd = (HWND)widget->GetNativeData(NS_NATIVE_WINDOW) Or at least to move GetScreenRectInAppUnitsExternal to the end of nsIFrame definition?įrame = presShell->GetPrimaryFrameFor(pContent) Is it possible to stop Firefox 3.0.2 release and to return back the API? RoboForm uses nsIFrame VFT from Firefox 3.0, and RoboForm call of nsIFrame->GetWindow() causes Firefox to crash.įirefox 3.0.* API shouldn't be changed since Firefox 3.0 release. Virtual method GetScreenRectInAppUnitsExternal has been added. NsIFrame interface has been changed in Firefox 3.0.2.
0 kommentar(er)
