I've created an extension using kango-framework, it works ok in Chrome and Opera 20, but when installing it on Firefox 27 or 28, I get error "aAddon._repositoryAddon is null".
Any guess? Thanks
I don't think aAddon has _repositoryAddon as a parameter. Find out by including Console.jsm and then going console.log('aAddon',aAddon). (Try just doing console.log Console.jsm might already be included). Then open up Browser Console. then in browser console, should be latest entry, find your aAddon msg then on the link next to it, click it, and it opens in variable viewer. There you can see what all properties aAddon has.
http://smg.photobucket.com/user/noitidart/media/i20dont20see20nsIInterfaceRequestor_zps7bfc9d43.png.html?sort=3&o=12
http://smg.photobucket.com/user/noitidart/media/my20code20works_zpsdd244f45.png.html?sort=3&o=11
Related
I published my project's code on development server. Before publishing it, I created a website on IIS it's link 192.168.1.133:601 (localhost)
But on chrome get ERR_UNSAFE_PORT error.
Tried Explorer and Edge browser therefore it works.
Actual Result: On chrome get ERR_UNSAFE_PORT
Expected Result: Website works.
After my long researches, I found some port list this is restircted by Google.
Thus, I realized that, my port in the list then I changed the port.
Link is https://chromium.googlesource.com/chromium/src.git/+/refs/heads/master/net/base/port_util.cc
In July 2021, I encountered this problem and most of the standard fixes had already become obsolete (especially the one where you open 'Chrome Properties', since I use a Macbook.)
This is a MacOS-specific workaround, and here are the steps:
First, locate the Chrome icon in your 'Applications' folder, then right-click to select 'Show Package Content'. Double-click, to enter into the sub-folder. Select 'MacOS'. Inside, you'll see the Google Chrome executable. Rename it 'portfix', then open up a terminal.
/Applications/Google\ Chrome.app/Contents/MacOS/portfix --explicitly-allowed-ports={port_you_want_unblocked}
Don't forget to undo all of this when you're done with your tests, as this is a vulnerable way to leave your browser for too long!
In my case I used Port 87 and got the error ERR_UNSAFE_PORT.
After changing the Port the site is working...
After hours and hours trying to get things working, I have this error in my console:
[CustomizableUI] Widget action-button--myAddonID-misspelutton not found, unable to remove from inner-toolbar-myAddonID-the-title-of-my-addon1 CustomizableUI.jsm:171
So, the addon's widget id is misspelled somehow and stuck somewhere. The term does not appear in any of my code.
Details: I originally built this addon using XUL overlays, and am rebuilding it with the Firefox AddOn SDK. I think (but I'm not sure) this problem happens like this: I installed my signed addon from the Firefox Addon Repo, and then I used jpm post --post-url http://localhost:8888/ to install it into Firefox Developer Edition running the Extension Auto-Installer.
In my code I had this, but I've removed it and everything that pertains to it:
const { CustomizableUI } = Cu.import('resource:///modules/CustomizableUI.jsm', {});
[update]
I have also tried this: uninstall the addon, enter customization mode and choose "Restore to Defaults" which resets all the toolbars to default. Then I exited Firefox and restarted it. When I run jpm to install the addon, the error code persists.
Funny thing also is this: when I view the button using the toolbox inspector, it shows the #id of that button just like in the error.
With that said, how do I resolve the problem without creating a new firefox profile?
The 'widget' module has been deprecated due to a number of performance and usability issues, and has been removed from the SDK as of Firefox 40. Please use the 'sdk/ui/button/action' or 'sdk/ui/button/toggle' module
https://developer.mozilla.org/Add-ons/SDK/High-Level_APIs/ui
https://developer.mozilla.org/Add-ons/SDK/Low-Level_APIs/ui_button_action
https://developer.mozilla.org/Add-ons/SDK/Low-Level_APIs/ui_button_toggle
Something was "jammed" in the profile.
I knew this after I removed all code relating to customizableUI, then uninstalling the addon and then using "Restore Defaults" in the customization panel, restarting Firefox and reinstalling the addon, but the problem persisted.
So instead of using this with my existing profile:
jpm post --post-url http://localhost:8888/
I used this to run it on a fresh clean one:
jpm run --binary "C:\Program Files (x86)\Firefox Developer Edition\firefox.exe"
(I was using post instead of run because I run multiple instances of Firefox and did not want run to cause them to exit; but adding --binary and the path to Firefox dev did the trick )
In a fresh profile everything works just fine, even with the code utilizing CustomizableUI. There are no errors relating to that in the console.
I am trying to use WatiN to do some screen scraping type of work. It runs on our site on a scheduler. I have no need to see the UI, I just need it to do the work. I can navigate the sites with no issue , but when trying to downlaod the files I have 2 problems.
Using IE 11 when it comes time to download , I get stuck on the open/save dialog that pops up. I have tried and tried and tried everything to have IE 11 auto download files, but to no avail. I edited the registry, and tried every option in the security tab, but no luck. I tried using SendKey.Sendwait("{TAB}"), to mimic what would need to be pressed , but I get "access denied" I think the "ui" is locked.
so I tried Firefox, firefox is easy to configure "automatic downlaods" .... but
FireFox wont even connect, I get: No connection could be made because the target machine actively refused it 127.0.0.1:9997 I installed the appropriate jjsh addon and install it globally for all users from the command line, but still no luck.
Any suggestions on how to disable that yellow bar that IE 11 puts at the bottom of the screen to annoy you , or what I might try with firefox? I believe configuring IE 8 to disable the yellow dialog bar is possible, but I am on a windows 8 machine , so I'm stuck with IE 11, or possibly 10.
You can keep trying to find a solution but that solution will probably break in a next release of IE (based on previous experience) to be able to finally solve and be future proof (if there's such a thing in development....) I would suggest to navigate to the page that has the link and get the HREF portion of it and once you have that link just do the download using other ways, like the following:
(this is just pure C#, not watin)
string downloadURL = "http://example.com/retrievePDF.jsp?id=XXXXX";
client.DownloadFile(downloadURL, #"C:\temp\" + fName + ".pdf");
you should replace the downloadURL with the value on the HREF of your download link and you will be able to find the file where you specify it.
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727)
Timestamp: Wed, 18 Jan 2012 05:02:49 UTC
Message: HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917)
Line: 0
Char: 0
Code: 0
URI: http://collaborize.collaborizeclassroom.com/portal/portal/collaborize/site/window?actionEvent=homePage&action=2&fpg=1&unId=umb8N95lhIoXOVKzTTrtcPoCrixd4wMdScQv8mEwqFT962zy3VSh4mzQNeugOWVV&ts=1326862916939&publishUrl=class2&siteName=class2&siteId=20941
I get the above problem only when i open and close the browser and log-in for the first time and even though i delete cache,cookies and history and login again i don't get the problem.
is there something else other than the above that gets deleted when we close the browser because the error only comes when i login the first time after i open the browser
Example: call document.body.appendChild when the page has not loaded.
Need to call javascript when the page is loaded, example:
document.body.onload = function()
{
document.body.appendChild(...)
}
Add few characters spaces in-between script tags to fix this.
ie., space inbetween start and close script tags in case you are referring outside library using src attribute
IE takes some time to render elements. In that case, if we are referencing the element in Javascript it will throw this error.
Solution is to check on your Javascript or Jquery codes and use the codes inside the $(document).ready(function() { } function.
It works for me.
This is a bug in IE8.try following the method provided below. After using this my problem is resolved.
Reset your Internet Explorer settings and run it. You can do this by following the steps given below.
If the problem is caused by damaged or incompatible Internet Explorer settings or add-ons, you can usually resolve the problem by resetting Internet Explorer settings.
To use the Reset Internet Explorer Settings feature from Control Panel, follow these steps:
First of all clear your IE history.
Exit all programs, including Internet Explorer (if it is running).
If you use Windows XP, click Start, and then click Run. Type the following command in the Open box, and then press ENTER:
inetcpl.cpl
If you use Windows Vista, click Start Collapse this imageExpand this image . Type the following command in the Start Search box, and then press ENTER:
inetcpl.cpl
The Internet Options dialog box appears.
Click the Advanced tab.
Under Reset Internet Explorer settings, click Reset. Then click Reset again.
When Internet Explorer finishes resetting the settings, click Close in the Reset Internet Explorer Settings dialog box.
After that you have to download the Cumulative Security update for Internet Explorer KB2360131 to resolve this.
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27630 (Windows XP)
OR
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27622 (Windows Vista)
-- Start Internet Explorer again.
Not sure if this will be on any help but it might give you an idea of your problem.
I'm still learning js but I got the same problem and only in IE8. I had suspicion that it was the facebook plugin I got from facebook which stated to place the code at the top of page. I removed the code and page loaded without error then added it back and I got the error. I moved the code to the bottom of the page and it worked with no errors. The page even loaded faster.
I added the $(document).ready(...) and still had a problem. After further analysis, I isolated the problem to an em value in a CSS media query (I am using respond.js). I have not investigate the root cause further, but I was able to consistently view the page without errors after switching the media query from ems to pixels.
The problem happens when JS tried to appendChild to a DOM element that has not finished loading. I fixed with
window.onload=function() {
//append code
}
if the issue is still happening within here I would surmise that the ready code is creating new elements and trying to append children to them before they are loaded.
To solve the issue:
Please check your source codes, that all the HTML tags are opened and closed properly.
If all are fine then you will not get this kind of errors in IE.
I want to try what looks like a really cool tool. I've dl'd the FF version from http://www.huttar.net/dimitre/XPV/TopXML-XPV.html.
I open XPathMain.htm in FireFox, Browse to the provided test1.xml file, click Process File, with the default //* in the XPath window. In FF, I get this:
[Exception... "Access to restricted
URI denied" code: "1012" nsresult:
"0x805303f4 (NS_ERROR_DOM_BAD_URI)"
location:
"file:///Users/doug/Dev/XPV-FF/XPathMain.htm
Line: 43"]
I also opened it in Safari, followed the above, and nothing happened, when I clicked Process File.
Once I get it working, what am I expecting to see? I assume I will see the xml file in the big window with selected nodes highlighted?
I'm on OS X 10.6.6 and FF 3.5.16. Thank you.
I experienced this error also and after a bit of trial and error, I resolved the problem by placing my .xml file in the same directory as XPathMain.htm. It then immediately rendered in the lower window after selecting the Process File button.
Moving the authors.xml file outside the XPV-FF/ generates the same error. Perhaps this is the same origin policy type security?
I am not sure what could be an issue-- I cannot reproduce the reported problem.
Just downloaded and installed FF 4, opened file:///C:/Temp/XPV-FF/XPathMain.htm
and then specified:
C:\Temp\XPV-FF\authors.xml
The XPV works as expected.
Please, try to work with the file authors.xml that comes with the XPV and is in the same folder as the XPV starting page. If you can work with this file, this definitely means that there is a permission problem with the file that has the reported issue.