Re: Run firefox as headless???
slimerjs is not fully headless unless using xvfb, is there anything else that can he used. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Run firefox as headless???
Is it possible to run firefox in headless form to fetch url and get the full Dom as rendered. Same way it would render on normal foredox ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
On Thursday, March 10, 2016 at 2:50:10 PM UTC-5, Kris Maglione wrote: > On Thu, Mar 10, 2016 at 10:44:24AM -0800, Devan Shah wrote: > >This happens in side extension only (works fine on web standalone), i will > >try to extract a simple reproducible scenario. > > > >Is there any way to simulate a extension env on web? > > If your problem is happening in an extension, then filing a bug > and attaching a testcase add-on is your best bet. > > If I had to guess based on what you've told us so far, I'd say > your problem has something to do with X-ray security > wrappers[1]. In general, properties that you add to X-ray > wrappers aren't visible to code running in other globals. I.e., > if you're accessing a web page from an SDK content script, your > view of the DOM nodes are different from the view the web page > sees. This also has implications for properties that you add to > prototypes. > > I don't know of any changes that would have significantly > changed the behavior in 45 vs previous versions, though, so a > testcase would be useful. > > [1]: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/Xray_vision Thanks Kris, I will take a look at Xray_vision and see if I can use it to create a simple reproducible testcase ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
On Thursday, March 10, 2016 at 2:42:14 PM UTC-5, Ted Mielczarek wrote: > On Thu, Mar 10, 2016, at 01:23 PM, Devan Shah wrote: > > hello > > > > When I set a custom property such as element.listofSomething = [] and > > then build the list and add it back to the same element. Then this > > element is passed to a function, now in that function I am no longer to > > access this property that I added to the function. > > > > Was there any sort of changes that would impact this? > > > > Also if I make use of Element.prototype to set a custom variable and try > > to access it for an element it is not available any more. IS there > > something that I am missing. (note this is when inside a plugin) > > FYI, I don't know what your particular bug is, but setting custom > properties on DOM elements is called "expandos", which might help you > file a more useful bug report: > https://developer.mozilla.org/en-US/docs/Glossary/Expando > > -Ted Thanks Ted, I will take a look at this. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Setting property on the element is no longer working on Firefox 45
On Thursday, March 10, 2016 at 1:32:41 PM UTC-5, Josh Matthews wrote: > Hi Devan! This is an interesting bug report, but it's lacking some > useful information to help triage it. Does this problem occur in a web > page, or extension, or some other environment? Can you create a minimal > example of the issue that anyone else could use to reproduce the problem > you're observing? > > Cheers, > Josh > > On 2016-03-10 1:23 PM, Devan Shah wrote: > > hello > > > > When I set a custom property such as element.listofSomething = [] and then > > build the list and add it back to the same element. Then this element is > > passed to a function, now in that function I am no longer to access this > > property that I added to the function. > > > > Was there any sort of changes that would impact this? > > > > Also if I make use of Element.prototype to set a custom variable and try to > > access it for an element it is not available any more. IS there something > > that I am missing. (note this is when inside a plugin) > > > > Thanks > > This happens in side extension only (works fine on web standalone), i will try to extract a simple reproducible scenario. Is there any way to simulate a extension env on web? Thanks ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Setting property on the element is no longer working on Firefox 45
hello When I set a custom property such as element.listofSomething = [] and then build the list and add it back to the same element. Then this element is passed to a function, now in that function I am no longer to access this property that I added to the function. Was there any sort of changes that would impact this? Also if I make use of Element.prototype to set a custom variable and try to access it for an element it is not available any more. IS there something that I am missing. (note this is when inside a plugin) Thanks ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: nsIDOMWindow is deprecated now is there an alternative?
Version 45, I am using the SDK from https://ftp.mozilla.org/pub/firefox/releases/45.0b4/win32/en-US/firefox-45.0b4.sdk.zip. Which I still see the nsIPromptFactory has /* void getPrompt (in nsIDOMWindow aParent, in nsIIDRef iid, [iid_is (iid), retval] out nsQIResult result); */ NS_IMETHOD GetPrompt(nsIDOMWindow *aParent, const nsIID & iid, void **result) = 0; <https://ftp.mozilla.org/pub/firefox/releases/45.0b4/win32/en-US/firefox-45.0b4.sdk.zip> On Wed, Feb 10, 2016 at 7:43 PM, Kyle Huey wrote: > Ok ... ignoring the question of how you're using it from C++ since binary > addons are gone, many of the methods on nsIDOMWindow moved to nsPIDOMWindow > and then to nsPIDOMWindowInner/Outer, depending on what version of Gecko > you're using. Today on trunk nsIPromptFactory takes a mozIDOMWindowProxy, > which is a base interface of nsPIDOMWindowOuter. You can look at > http://mxr.mozilla.org/mozilla-central/source/dom/base/nsPIDOMWindow.h to > see what's there. Some methods on nsIDOMWindow that were unused were > removed completely, though I don't think there were many. > > - Kyle > > On Wed, Feb 10, 2016 at 4:40 PM, Devan Shah > wrote: > >> I am using it from c++ >> >> On Wed, Feb 10, 2016 at 7:38 PM, Kyle Huey wrote: >> >>> Are you using it from JS or C++? If you're using it from JS, nothing >>> has changed. >>> >>> - Kyle >>> >>> On Wed, Feb 10, 2016 at 4:32 PM, Devan Shah >>> wrote: >>> >>>> Hello >>>> >>>> nsIDOMWindow is deprecated now according to: >>>> https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIDOMWindow >>>> is there an alternative for this interface. I am using a lot of functions >>>> from this interface and also using nsIPromptFactory which relies on >>>> nsIDOMWindow a lot for all of it functions. >>>> >>>> Is there any way to get an alternative with the same functionality >>>> which requires minimal changes or is there a way that I can get the >>>> nsIDOMWindow interface and all of its functionality back by adding the >>>> interface locally and implementing the functions locally. >>>> >>>> Thanks >>>> Devan Shah >>>> ___ >>>> dev-platform mailing list >>>> dev-platform@lists.mozilla.org >>>> https://lists.mozilla.org/listinfo/dev-platform >>>> >>> >>> >> > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: nsIDOMWindow is deprecated now is there an alternative?
yep
This is how I was using nsIDOMWindow before:
NS_IMETHODIMP WebBrowserChrome::OnLocationChange(nsIWebProgress*
aWebProgress,
nsIRequest* aRequest,
nsIURI *location,
uint32_t aFlags)
{
PRBool isSubFrameLoad = PR_FALSE; // Is this a subframe load
if (aWebProgress) {
nsCOMPtr domWindow;
nsCOMPtr topDomWindow;
aWebProgress->GetDOMWindow(getter_AddRefs(domWindow));
if (domWindow) { // Get root domWindow
domWindow->GetTop(getter_AddRefs(topDomWindow));
}
if (domWindow != topDomWindow)
isSubFrameLoad = PR_TRUE;
}
if (!isSubFrameLoad)
CWebBrowserChromeUI::UpdateCurrentURI(this);
return NS_OK;
}
So here just changing nsCOMPtr to nsCOMPtr and
using QueryInterface should do the trick right?
Also I am using a function called SizeToContent() from nsIDOMWindow which I
do not see exists any more in nsPIDOMWindow either was this one removed
completly.
On Wed, Feb 10, 2016 at 8:24 PM, Kyle Huey wrote:
> Right, that will work, although you could nsCOMPtr to make it a lot
> prettier:
>
> void test(nsIDOMWindow* aDOMWindow, nsIBaseWindow** aBaseWindow)
> {
> nsCOMPtr window = do_QueryInterface(aDOMWindow);
> nsCOMPtr docShell;
> if (window)
> window->GetDocShell(getter_AddRefs(docShell));
> nsIWebShell* rootWebShell = 0;
> NS_IF_RELEASE(rootWebShell);
> //return status;
> }
>
> - Kyle
>
> On Wed, Feb 10, 2016 at 5:22 PM, Devan Shah
> wrote:
>
>> Do you happen to have a QueryInterface example,
>>
>> Would something like the following work:
>>
>> void test(nsIDOMWindow* aDOMWindow, nsIBaseWindow** aBaseWindow)
>> {
>> nsPIDOMWindow* window = 0;
>> nsresult status = aDOMWindow->QueryInterface(NS_GET_IID(nsPIDOMWindow),
>> (void**)&window);
>> nsIDocShell* docShell = 0;
>> if (window)
>> window->GetDocShell(&docShell);
>> nsIWebShell* rootWebShell = 0;
>> NS_IF_RELEASE(rootWebShell);
>> NS_IF_RELEASE(docShell);
>> NS_IF_RELEASE(window);
>> //return status;
>> }
>>
>> On Wed, Feb 10, 2016 at 8:16 PM, Kyle Huey wrote:
>>
>>> Alright, just QueryInterface between nsIDOMWindow and nsPIDOMWindow when
>>> you have one and need the other and you should be fine.
>>>
>>> - Kyle
>>>
>>> On Wed, Feb 10, 2016 at 5:15 PM, Devan Shah
>>> wrote:
>>>
>>>> Currently I just want to get it up and running again on FF 45 again,
>>>> with out making too much changes because we plan to deprecate this feature
>>>> mid this year or so.
>>>>
>>>> Just need to get it working on Firefox 45, currently works perfectly on
>>>> Firefox 38.
>>>>
>>>>
>>>
>>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Re: nsIDOMWindow is deprecated now is there an alternative?
So Something like:
NS_IMETHODIMP WebBrowserChrome::OnLocationChange(nsIWebProgress*
aWebProgress,
nsIRequest* aRequest,
nsIURI *location,
uint32_t aFlags)
{
PRBool isSubFrameLoad = PR_FALSE; // Is this a subframe load
if (aWebProgress) {
nsCOMPtr domWindow;
nsCOMPtr topDomWindow;
aWebProgress->GetDOMWindow(getter_AddRefs(domWindow));
if (domWindow) { // Get root domWindow
topDomWindow = do_QueryInterface(domWindow);
topDomWindow->GetTop();
}
if (domWindow != topDomWindow)
isSubFrameLoad = PR_TRUE;
}
if (!isSubFrameLoad)
CWebBrowserChromeUI::UpdateCurrentURI(this);
return NS_OK;
}
On Wed, Feb 10, 2016 at 8:37 PM, Kyle Huey wrote:
> You get the nsIDOMWindow, and then QueryInterface to nsPIDOMWindow to call
> GetTop on it.
>
> - Kyle
>
> On Wed, Feb 10, 2016 at 5:35 PM, Devan Shah
> wrote:
>
>> In the below code i use aWebProgress to and then GetDOMWindow on that,
>> however GetDOMWindow only allows nsIDOMWindow, would the QueryInterface
>> accommodate for this for this
>>
>> NS_IMETHODIMP WebBrowserChrome::OnLocationChange(nsIWebProgress*
>> aWebProgress,
>> nsIRequest* aRequest,
>> nsIURI *location,
>> uint32_t aFlags)
>> {
>> PRBool isSubFrameLoad = PR_FALSE; // Is this a subframe load
>> if (aWebProgress) {
>> nsCOMPtr domWindow;
>> nsCOMPtr topDomWindow;
>> aWebProgress->GetDOMWindow(getter_AddRefs(domWindow));
>> if (domWindow) { // Get root domWindow
>> domWindow->GetTop(getter_AddRefs(topDomWindow));
>> }
>> if (domWindow != topDomWindow)
>> isSubFrameLoad = PR_TRUE;
>> }
>> if (!isSubFrameLoad)
>> CWebBrowserChromeUI::UpdateCurrentURI(this);
>> return NS_OK;
>> }
>>
>> On Wed, Feb 10, 2016 at 8:30 PM, Kyle Huey wrote:
>>
>>> Yes, SizeToContent is only accessible to JS now.
>>>
>>> - Kyle
>>>
>>> On Wed, Feb 10, 2016 at 5:28 PM, Devan Shah
>>> wrote:
>>>
>>>> yep
>>>>
>>>> This is how I was using nsIDOMWindow before:
>>>>
>>>> NS_IMETHODIMP WebBrowserChrome::OnLocationChange(nsIWebProgress*
>>>> aWebProgress,
>>>> nsIRequest* aRequest,
>>>> nsIURI *location,
>>>> uint32_t aFlags)
>>>> {
>>>> PRBool isSubFrameLoad = PR_FALSE; // Is this a subframe load
>>>> if (aWebProgress) {
>>>> nsCOMPtr domWindow;
>>>> nsCOMPtr topDomWindow;
>>>> aWebProgress->GetDOMWindow(getter_AddRefs(domWindow));
>>>> if (domWindow) { // Get root domWindow
>>>> domWindow->GetTop(getter_AddRefs(topDomWindow));
>>>> }
>>>> if (domWindow != topDomWindow)
>>>> isSubFrameLoad = PR_TRUE;
>>>> }
>>>> if (!isSubFrameLoad)
>>>> CWebBrowserChromeUI::UpdateCurrentURI(this);
>>>> return NS_OK;
>>>> }
>>>>
>>>> So here just changing nsCOMPtr to nsCOMPtr
>>>> and using QueryInterface should do the trick right?
>>>>
>>>> Also I am using a function called SizeToContent() from nsIDOMWindow
>>>> which I do not see exists any more in nsPIDOMWindow either was this one
>>>> removed completly.
>>>>
>>>> On Wed, Feb 10, 2016 at 8:24 PM, Kyle Huey wrote:
>>>>
>>>>> Right, that will work, although you could nsCOMPtr to make it a lot
>>>>> prettier:
>>>>>
>>>>> void test(nsIDOMWindow* aDOMWindow, nsIBaseWindow** aBaseWindow)
>>>>> {
>>>>> nsCOMPtr window = do_QueryInterface(aDOMWindow);
>>>>> nsCOMPtr docShell;
>>>>> if (window)
>>>>> window->GetDocShell(getter_AddRefs(docShell));
>>>>> nsIWebShell* rootWebShell = 0;
>>>>> NS_IF_RELEASE(rootWebShell);
>>>>> //return status;
>>>>> }
>>>>>
>>>>> - Kyle
>>>>>
>>>>> On Wed, Feb 10, 2016 at 5:22 PM, Devan Shah
>>>>> wrote:
>>>>>
>>>>>> Do you happen to have a QueryInterface example,
>>>>>>
>>>>>> Would something like the following work:
>>>>>>
>>>>>> void test(nsIDOMWindow* aDOM
Re: nsIDOMWindow is deprecated now is there an alternative?
I tried to use nsPIDOMWindow, but issues is that functions like: Function GetContentDOMWindow in nsIWebBrowser is expecting: NS_IMETHOD GetContentDOMWindow(nsIDOMWindow * *aContentDOMWindow) = 0; (firefox-45.0b4\firefox-sdk\include\nsIWebBrowser.h) Function: NS_IMETHOD GetPrompt(nsIDOMWindow *aParent, const nsIID & iid, void **result) = 0; from nsIPromptFactory So makes it all not compatible. Is there any way I can rebuild the Firefox SDK with the old nsIDOMWindow On Wed, Feb 10, 2016 at 7:51 PM, Kyle Huey wrote: > Yeah, ok, nsPIDOMWindow then. > > - Kyle > > On Wed, Feb 10, 2016 at 4:49 PM, Devan Shah > wrote: > >> Version 45, I am using the SDK from >> https://ftp.mozilla.org/pub/firefox/releases/45.0b4/win32/en-US/firefox-45.0b4.sdk.zip. >> Which I still see the nsIPromptFactory has >> >> /* void getPrompt (in nsIDOMWindow aParent, in nsIIDRef iid, [iid_is >> (iid), retval] out nsQIResult result); */ >> NS_IMETHOD GetPrompt(nsIDOMWindow *aParent, const nsIID & iid, void >> **result) = 0; >> >> >> >> <https://ftp.mozilla.org/pub/firefox/releases/45.0b4/win32/en-US/firefox-45.0b4.sdk.zip> >> >> On Wed, Feb 10, 2016 at 7:43 PM, Kyle Huey wrote: >> >>> Ok ... ignoring the question of how you're using it from C++ since >>> binary addons are gone, many of the methods on nsIDOMWindow moved to >>> nsPIDOMWindow and then to nsPIDOMWindowInner/Outer, depending on what >>> version of Gecko you're using. Today on trunk nsIPromptFactory takes a >>> mozIDOMWindowProxy, which is a base interface of nsPIDOMWindowOuter. You >>> can look at >>> http://mxr.mozilla.org/mozilla-central/source/dom/base/nsPIDOMWindow.h >>> to see what's there. Some methods on nsIDOMWindow that were unused were >>> removed completely, though I don't think there were many. >>> >>> - Kyle >>> >>> On Wed, Feb 10, 2016 at 4:40 PM, Devan Shah >>> wrote: >>> >>>> I am using it from c++ >>>> >>>> On Wed, Feb 10, 2016 at 7:38 PM, Kyle Huey wrote: >>>> >>>>> Are you using it from JS or C++? If you're using it from JS, nothing >>>>> has changed. >>>>> >>>>> - Kyle >>>>> >>>>> On Wed, Feb 10, 2016 at 4:32 PM, Devan Shah >>>>> wrote: >>>>> >>>>>> Hello >>>>>> >>>>>> nsIDOMWindow is deprecated now according to: >>>>>> https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIDOMWindow >>>>>> is there an alternative for this interface. I am using a lot of functions >>>>>> from this interface and also using nsIPromptFactory which relies on >>>>>> nsIDOMWindow a lot for all of it functions. >>>>>> >>>>>> Is there any way to get an alternative with the same functionality >>>>>> which requires minimal changes or is there a way that I can get the >>>>>> nsIDOMWindow interface and all of its functionality back by adding the >>>>>> interface locally and implementing the functions locally. >>>>>> >>>>>> Thanks >>>>>> Devan Shah >>>>>> ___ >>>>>> dev-platform mailing list >>>>>> dev-platform@lists.mozilla.org >>>>>> https://lists.mozilla.org/listinfo/dev-platform >>>>>> >>>>> >>>>> >>>> >>> >> > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: nsIDOMWindow is deprecated now is there an alternative?
In the below code i use aWebProgress to and then GetDOMWindow on that,
however GetDOMWindow only allows nsIDOMWindow, would the QueryInterface
accommodate for this for this
NS_IMETHODIMP WebBrowserChrome::OnLocationChange(nsIWebProgress*
aWebProgress,
nsIRequest* aRequest,
nsIURI *location,
uint32_t aFlags)
{
PRBool isSubFrameLoad = PR_FALSE; // Is this a subframe load
if (aWebProgress) {
nsCOMPtr domWindow;
nsCOMPtr topDomWindow;
aWebProgress->GetDOMWindow(getter_AddRefs(domWindow));
if (domWindow) { // Get root domWindow
domWindow->GetTop(getter_AddRefs(topDomWindow));
}
if (domWindow != topDomWindow)
isSubFrameLoad = PR_TRUE;
}
if (!isSubFrameLoad)
CWebBrowserChromeUI::UpdateCurrentURI(this);
return NS_OK;
}
On Wed, Feb 10, 2016 at 8:30 PM, Kyle Huey wrote:
> Yes, SizeToContent is only accessible to JS now.
>
> - Kyle
>
> On Wed, Feb 10, 2016 at 5:28 PM, Devan Shah
> wrote:
>
>> yep
>>
>> This is how I was using nsIDOMWindow before:
>>
>> NS_IMETHODIMP WebBrowserChrome::OnLocationChange(nsIWebProgress*
>> aWebProgress,
>> nsIRequest* aRequest,
>> nsIURI *location,
>> uint32_t aFlags)
>> {
>> PRBool isSubFrameLoad = PR_FALSE; // Is this a subframe load
>> if (aWebProgress) {
>> nsCOMPtr domWindow;
>> nsCOMPtr topDomWindow;
>> aWebProgress->GetDOMWindow(getter_AddRefs(domWindow));
>> if (domWindow) { // Get root domWindow
>> domWindow->GetTop(getter_AddRefs(topDomWindow));
>> }
>> if (domWindow != topDomWindow)
>> isSubFrameLoad = PR_TRUE;
>> }
>> if (!isSubFrameLoad)
>> CWebBrowserChromeUI::UpdateCurrentURI(this);
>> return NS_OK;
>> }
>>
>> So here just changing nsCOMPtr to nsCOMPtr
>> and using QueryInterface should do the trick right?
>>
>> Also I am using a function called SizeToContent() from nsIDOMWindow which
>> I do not see exists any more in nsPIDOMWindow either was this one removed
>> completly.
>>
>> On Wed, Feb 10, 2016 at 8:24 PM, Kyle Huey wrote:
>>
>>> Right, that will work, although you could nsCOMPtr to make it a lot
>>> prettier:
>>>
>>> void test(nsIDOMWindow* aDOMWindow, nsIBaseWindow** aBaseWindow)
>>> {
>>> nsCOMPtr window = do_QueryInterface(aDOMWindow);
>>> nsCOMPtr docShell;
>>> if (window)
>>> window->GetDocShell(getter_AddRefs(docShell));
>>> nsIWebShell* rootWebShell = 0;
>>> NS_IF_RELEASE(rootWebShell);
>>> //return status;
>>> }
>>>
>>> - Kyle
>>>
>>> On Wed, Feb 10, 2016 at 5:22 PM, Devan Shah
>>> wrote:
>>>
>>>> Do you happen to have a QueryInterface example,
>>>>
>>>> Would something like the following work:
>>>>
>>>> void test(nsIDOMWindow* aDOMWindow, nsIBaseWindow** aBaseWindow)
>>>> {
>>>> nsPIDOMWindow* window = 0;
>>>> nsresult status =
>>>> aDOMWindow->QueryInterface(NS_GET_IID(nsPIDOMWindow), (void**)&window);
>>>> nsIDocShell* docShell = 0;
>>>> if (window)
>>>> window->GetDocShell(&docShell);
>>>> nsIWebShell* rootWebShell = 0;
>>>> NS_IF_RELEASE(rootWebShell);
>>>> NS_IF_RELEASE(docShell);
>>>> NS_IF_RELEASE(window);
>>>> //return status;
>>>> }
>>>>
>>>> On Wed, Feb 10, 2016 at 8:16 PM, Kyle Huey wrote:
>>>>
>>>>> Alright, just QueryInterface between nsIDOMWindow and nsPIDOMWindow
>>>>> when you have one and need the other and you should be fine.
>>>>>
>>>>> - Kyle
>>>>>
>>>>> On Wed, Feb 10, 2016 at 5:15 PM, Devan Shah
>>>>> wrote:
>>>>>
>>>>>> Currently I just want to get it up and running again on FF 45 again,
>>>>>> with out making too much changes because we plan to deprecate this
>>>>>> feature
>>>>>> mid this year or so.
>>>>>>
>>>>>> Just need to get it working on Firefox 45, currently works perfectly
>>>>>> on Firefox 38.
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Re: nsIDOMWindow is deprecated now is there an alternative?
I am using it from c++ On Wed, Feb 10, 2016 at 7:38 PM, Kyle Huey wrote: > Are you using it from JS or C++? If you're using it from JS, nothing has > changed. > > - Kyle > > On Wed, Feb 10, 2016 at 4:32 PM, Devan Shah > wrote: > >> Hello >> >> nsIDOMWindow is deprecated now according to: >> https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIDOMWindow >> is there an alternative for this interface. I am using a lot of functions >> from this interface and also using nsIPromptFactory which relies on >> nsIDOMWindow a lot for all of it functions. >> >> Is there any way to get an alternative with the same functionality which >> requires minimal changes or is there a way that I can get the nsIDOMWindow >> interface and all of its functionality back by adding the interface locally >> and implementing the functions locally. >> >> Thanks >> Devan Shah >> ___ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform >> > > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: nsIDOMWindow is deprecated now is there an alternative?
Currently I just want to get it up and running again on FF 45 again, with out making too much changes because we plan to deprecate this feature mid this year or so. Just need to get it working on Firefox 45, currently works perfectly on Firefox 38. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: nsIDOMWindow is deprecated now is there an alternative?
I was using the xulrunner SDK, but that is no longer created any more so using the firefox SDK. I am using it to create a plugin which can be used to launch a web browser which communicates with a proxy server which can be used to capture all the http traffic. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: nsIDOMWindow is deprecated now is there an alternative?
Do you happen to have a QueryInterface example,
Would something like the following work:
void test(nsIDOMWindow* aDOMWindow, nsIBaseWindow** aBaseWindow)
{
nsPIDOMWindow* window = 0;
nsresult status = aDOMWindow->QueryInterface(NS_GET_IID(nsPIDOMWindow),
(void**)&window);
nsIDocShell* docShell = 0;
if (window)
window->GetDocShell(&docShell);
nsIWebShell* rootWebShell = 0;
NS_IF_RELEASE(rootWebShell);
NS_IF_RELEASE(docShell);
NS_IF_RELEASE(window);
//return status;
}
On Wed, Feb 10, 2016 at 8:16 PM, Kyle Huey wrote:
> Alright, just QueryInterface between nsIDOMWindow and nsPIDOMWindow when
> you have one and need the other and you should be fine.
>
> - Kyle
>
> On Wed, Feb 10, 2016 at 5:15 PM, Devan Shah
> wrote:
>
>> Currently I just want to get it up and running again on FF 45 again, with
>> out making too much changes because we plan to deprecate this feature mid
>> this year or so.
>>
>> Just need to get it working on Firefox 45, currently works perfectly on
>> Firefox 38.
>>
>>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
nsIDOMWindow is deprecated now is there an alternative?
Hello nsIDOMWindow is deprecated now according to: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIDOMWindow is there an alternative for this interface. I am using a lot of functions from this interface and also using nsIPromptFactory which relies on nsIDOMWindow a lot for all of it functions. Is there any way to get an alternative with the same functionality which requires minimal changes or is there a way that I can get the nsIDOMWindow interface and all of its functionality back by adding the interface locally and implementing the functions locally. Thanks Devan Shah ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: XULRunner future and ownership
On Wednesday, February 10, 2016 at 11:48:24 AM UTC-5, Dave Townsend wrote: > On Wed, Feb 10, 2016 at 8:39 AM, Devan Shah wrote: > > On Wednesday, February 10, 2016 at 10:43:44 AM UTC-5, Dave Townsend wrote: > >> I'm not sure why that page links to the nightly builds but the release > >> versions are here: http://archive.mozilla.org/pub/firefox/releases/ > >> > >> Note that Firefox 45 hasn't been released yet so the latest SDK is for > >> one of the beta versions. > >> > >> On Wed, Feb 10, 2016 at 7:21 AM, Devan Shah wrote: > >> > On Wednesday, July 29, 2015 at 2:30:54 PM UTC-4, Benjamin Smedberg wrote: > >> >> The Mozilla project no longer sees XULRunner as a priority project. It's > >> >> not core to advancing the open web or any of our current or planned > >> >> products. > >> >> > >> >> As Ben Hearsum noted a couple weeks ago, we are turning off automated > >> >> XULRunner builds and so XULRunner will probably quickly cease to work. > >> >> In order to keep XULRunner in the tree, we need an owner who wants to > >> >> keep it building and running properly. Currently, I am the nominal owner > >> >> of the XULRunner code, but I have no desire to do this work or even > >> >> really to review the necessary patches. I am looking to see whether > >> >> there is an alternate owner who is interested in the task of keeping > >> >> XULRunner building and running properly and reviewing patches to > >> >> XULRuner-specific code. Please contact me if you want to nominate > >> >> yourself or somebody else for this role. > >> >> > >> >> If I do not find a suitable owner in the next two weeks, I intend to > >> >> remove the XULRunner code from the mozilla-central repository on > >> >> 14-August. > >> >> > >> >> --BDS > >> > > >> > Hello > >> > > >> > Is the xulrunner SDK officially deprecated now. I see that the latest > >> > xulrunner version is xulrunner-41.0.2 would this be compatible wit > >> > Firefox 45. If not where can I get a version that is compatible with > >> > Firefox 45. I see that > >> > http://ftp.mozilla.org/pub/xulrunner/nightly/latest-trunk/Deprecation_notice.txt > >> > points to: > >> > > >> > XULRunner SDKs can now be downloaded from > >> > > >> > https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ > >> > > >> > Theses are the nightly builds, but where can I get the release version > >> > for Firefox 45. Also does the SDK change from Firefox 45 to Firefox 45 > >> > ESR. > >> > > >> > Thanks > >> > Devan Shah > >> > ___ > >> > dev-platform mailing list > >> > dev-platform@lists.mozilla.org > >> > https://lists.mozilla.org/listinfo/dev-platform > > > > So xulrunner SDK version 41.0.2 will not work with FF 45 right. > > Correct, you must use the matching version. Thanks ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: XULRunner future and ownership
On Wednesday, February 10, 2016 at 10:43:44 AM UTC-5, Dave Townsend wrote: > I'm not sure why that page links to the nightly builds but the release > versions are here: http://archive.mozilla.org/pub/firefox/releases/ > > Note that Firefox 45 hasn't been released yet so the latest SDK is for > one of the beta versions. > > On Wed, Feb 10, 2016 at 7:21 AM, Devan Shah wrote: > > On Wednesday, July 29, 2015 at 2:30:54 PM UTC-4, Benjamin Smedberg wrote: > >> The Mozilla project no longer sees XULRunner as a priority project. It's > >> not core to advancing the open web or any of our current or planned > >> products. > >> > >> As Ben Hearsum noted a couple weeks ago, we are turning off automated > >> XULRunner builds and so XULRunner will probably quickly cease to work. > >> In order to keep XULRunner in the tree, we need an owner who wants to > >> keep it building and running properly. Currently, I am the nominal owner > >> of the XULRunner code, but I have no desire to do this work or even > >> really to review the necessary patches. I am looking to see whether > >> there is an alternate owner who is interested in the task of keeping > >> XULRunner building and running properly and reviewing patches to > >> XULRuner-specific code. Please contact me if you want to nominate > >> yourself or somebody else for this role. > >> > >> If I do not find a suitable owner in the next two weeks, I intend to > >> remove the XULRunner code from the mozilla-central repository on 14-August. > >> > >> --BDS > > > > Hello > > > > Is the xulrunner SDK officially deprecated now. I see that the latest > > xulrunner version is xulrunner-41.0.2 would this be compatible wit Firefox > > 45. If not where can I get a version that is compatible with Firefox 45. I > > see that > > http://ftp.mozilla.org/pub/xulrunner/nightly/latest-trunk/Deprecation_notice.txt > > points to: > > > > XULRunner SDKs can now be downloaded from > >https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ > > > > Theses are the nightly builds, but where can I get the release version for > > Firefox 45. Also does the SDK change from Firefox 45 to Firefox 45 ESR. > > > > Thanks > > Devan Shah > > ___ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform So xulrunner SDK version 41.0.2 will not work with FF 45 right. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: XULRunner future and ownership
On Wednesday, July 29, 2015 at 2:30:54 PM UTC-4, Benjamin Smedberg wrote: > The Mozilla project no longer sees XULRunner as a priority project. It's > not core to advancing the open web or any of our current or planned > products. > > As Ben Hearsum noted a couple weeks ago, we are turning off automated > XULRunner builds and so XULRunner will probably quickly cease to work. > In order to keep XULRunner in the tree, we need an owner who wants to > keep it building and running properly. Currently, I am the nominal owner > of the XULRunner code, but I have no desire to do this work or even > really to review the necessary patches. I am looking to see whether > there is an alternate owner who is interested in the task of keeping > XULRunner building and running properly and reviewing patches to > XULRuner-specific code. Please contact me if you want to nominate > yourself or somebody else for this role. > > If I do not find a suitable owner in the next two weeks, I intend to > remove the XULRunner code from the mozilla-central repository on 14-August. > > --BDS Hello Is the xulrunner SDK officially deprecated now. I see that the latest xulrunner version is xulrunner-41.0.2 would this be compatible wit Firefox 45. If not where can I get a version that is compatible with Firefox 45. I see that http://ftp.mozilla.org/pub/xulrunner/nightly/latest-trunk/Deprecation_notice.txt points to: XULRunner SDKs can now be downloaded from https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ Theses are the nightly builds, but where can I get the release version for Firefox 45. Also does the SDK change from Firefox 45 to Firefox 45 ESR. Thanks Devan Shah ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
