Ok so I have a basic bookmarklet that opens remote websites. However when I try to open my local dev site it just opens to a blank page. I am assuming this has something to do with security etc.
I set the bookmarklet to open one of my remote sites, gnull.com - This worked fine. I then set gnull.com to resolve to 127.0.0.1 and changed my bindings in IIS. The result this time is that a new window opens however it is blank. When I look at the headers being sent only one is created with a result of 'error' and a type of 'NS_ERROR_ABORT'.
I am using Firefox 4 on Windows 7. Does anyone know how to setup bookmarklets for testing local sites? The code itself works fine since I have tested this with other live websites so this appears to be a browser security feature.
So as I mentioned in the comment, I found the issue was with ABE - a component of the noscript extension. ABE blocks scripts from accessing local resources, in my case a local website. I disabled ABE in the noscript options and everything works fine.
Related
I have made small web-app: http://letme.ijn.su
At this moment I debug it on PC.
I have problems with Firefox - when I make some changes on server side(add more notes) and resfresh page - I see changes only after some time. Other browsers(chrome, opera, yandex) work well
I suppose it is because of firefox cashing - how can I force it to get new info from server with every request?
I use Ubuntu, Apache, PHP.
by link http://letme.ijn.su - you launch index.php, which print job-page or login-page(have you cookies or not).
Maybe this will work clearstatcache(); This should clear the cache on the server side. Or if you want to delete a file you can use unlink();
I think clearing your browser cache will work best. Also, make sure to check the "Disable Cache" is the inspector settings. You can also try "View Page Source" in Firefox and refresh the newly-opened tab containing the page source.
At my workplace, there is a website we regularly visit to obtain some information. Upon clicking a link in the page, a new window opens and displays the information. This currently works fine in IE8+, but the link is dead in chrome. I've checked and after researching, I believe that chrome is blocking from a new window to open due to security measures. I get no warnings or pop ups, JavaScript is enabled, pop up is allowed for all sites, so now I'm a bit stuck. Is there a built in command to access the chrome features and enable to open new windows? We are using chrome mostly and would like to resolve on this browser. The onclick script looks like this:
onclick="javascript:OpenW('ViewInvoiceEstimate.asp?EIID=2984252&EI=I&Tabname=OPEN')
When I attached the link section of the script as the suffix to the web address, the content shows up fine from the same web browser.
I'm experiencing a strange intermittent issue with Chrome Developer tools hanging on to old versions of JavaScript files. I'll be developing some JS app, things humming along just find, and then all the sudden my JavaScript files will disappear from the list of JavaScript files on the "sources" tab. This is my first clue that something is wrong.
What I eventually discovered is that Chrome Developer Tools is, apparently hanging on to an old version of the JavaScript file. Chrome itself is requesting and executing the latest version from the server, but you can't debug the JavaScript file.
I "proved" to myself that this was what's happening by taking a particular JavaScript file that had disappeared from my sources list, and replacing it with a one line console.log statement.
I then reloaded the page, and noted that the console.log statement appeared in the JavaScript console. I also noted in the Network tab that the JavaScript file was successfully retrieved, and that what came down over the wire contained just the one line console.log statement.
However, the JavaScript file still didn't appear in the sources list, and if I clicked on the filename in the console (where it appears on the righthand side of the console, next to the logged statement), then I jump to the sources tab, and an old version of the JavaScript file is opened.
This JavaScript file is loaded onto the page via a regular <script> tag. It is not loaded dynamically, via another script, or via eval. Just a plain, vanilla <script> tag that points to the .js file on the webserver.
I've tried:
Ensuring that "Disable cache (while DevTools is open)" is checked in the DevTools settings.
Manually clearing out my cache and cookies in Chrome.
Restarting Chrome
Manually loading the JavaScript file in a separate Chrome tab
Disabling every Chrome extension/app that I have installed
Running the page in incognito mode
Uncheck both "Enable JavaScript source maps" and "Enable CSS source maps"
None of these changed the behavior. You can watch a video demonstrating this here, if you don't believe me!
I do think it's a Chrome issue, as I can use Firefox without this issue... but I really like Chrome and Chrome's developer tools :-) So I'd like to get this working in Chrome...
Update I reported this as a Chrome bug here. If this bug is affecting you, or important to you, please vote it up and/or add comments with additional information.
Chrome DevTools works fine for me. When I load it for a page it remembers beyond the lifespan of the chrome process what sources I have open; although it gets the order wrong. I see two differences in our devtools prefs: disable cache and enable maps. So I would advise:
1) uncheck disable cache (while DevTools is open),
2) (if 1 didn't work) press the "Restore defaults and reload" button.
The issue persists in 78.0.3904.97. To fix it run settings > advanced > reset.
Some code editors such as rubymine cache js files.
To solve for rubymine: File > Invalidate Cache/Restart
As suggested here https://groups.google.com/d/msg/google-chrome-developer-tools/2rolf--fJ3M/UTJQaZN3K28J, for development environment I added these headers when serving a sourcemap:
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: 0
and it seems to do the job (at least for now).
I am using the Google+ Javascript API log in button and it works perfectly fine in Chrome on Windows and Android. It also works perfectly fine in Safari on an iPad and iPhone. However, when using Chrome on the iPad or iPhone, the pop-up tab for the Google log in never returns after clicking to allow access. It seems to be submitting the form to the pop-up tab and never directing back to the original tab. Any ideas?
Google knows about this issue, but currently cannot do anything about it. It comes down to window.open not working in UIWebview.
Safari is not limited by App Store rules the way all third-party apps
are. Apple can use any WebKit APIs they want to, whereas we are
constrained to what is possible using UIWebView.
They encourage anyone facing this issue to open a bug with Apple.
You can't make Apple do anything, but anyone affected by this can
file a bug against Apple about the fact that UIWebView doesn't support
window.open and subsequent cross-site scripting, to clearly
communicate demand for that support.
There's no way for people to add votes or comments to existing Apple
bug reports, so the usual advice is for everyone to file their own.
Here's the URL for bug reporting in Apple: https://bugreport.apple.com
Here is a sample bug posting to Apple provided by one of the users:
Summary: Please add support for window.open and subsequent cross-site
scripting to UIWebView. This is blocking Facebook/Twitter/etc login
workflows in Chrome for iOS for example
Steps to Reproduce:
1. In a tab, open a page that runs the code var w = window.open(yourURL, null, null);
2. The page at yourURL should try to accesswindow.opener`, such as to postMessage back to the original page
3. Don't profit.
Expected Results: New window can access window.opener.
Actual Results: window.opener is undefined.
Version:
7.0.4
Notes:
Configuration: Chrome Version (from "Settings > About Google Chrome"):
19.0.1084.60 Device Type: iPad 3
You can follow the issue thread for updates.
I am very new to FB programming and JavaScript as well (a long time ASP.NET programmer). I am trying to use the JavaScript SDK to create a fangate. The page works perfectly when I run my page directly (http://wmssupportforum.com/FacebookPages/FacebookWMSJobs.aspx), but when it is pulled up from within my Fan Page (http://www.facebook.com/pages/WMS-Support-Forum/207356652683205?sk=app_143965989047095), it doesn't work, i.e. it doesn't Show my Liked div and hide my UnLiked div, etc.
I have no idea how to debug this from within FB...(when I render it in IE directly from my site, I can debug it, but when I try to debug the Fan Page version, IE's dev tools won't load the script to debug it...it just hangs).
Any help is greatly appreciated!!!
Thanks in advance,
Chad
UPDATE: It looks like the difference is only an issue in IE v9. I don't have the same issues in Firefox or Chrome. So in IE9, pulling my page up on one IE Browser tab directly at the page URL works, but when pulled up through my FB FanPage on another IE tab, it doesn't work...seems like it is hanging as the HTML tab in IE Developer Tools window just says Loading....
It's a webserver issue. Believe it or not, but by adding in a simple P3P header to your response will solve the IE issue. See: Cookie blocked/not saved in IFRAME in Internet Explorer and also http://www.hanselman.com/blog/TheImportanceOfP3PAndACompactPrivacyPolicy.aspx