(I added this post to a long series at Github of similar/recent experiences. I'm hoping someone here has an answer.)
Oh, good, I'm not just stoopid.
Trying to learn Angular on my own, from a book. When it calls out the use of batarang to show scope and models for a small sample script, and I fire up batarang, all I get is 'Scopes' over 'Scope()' on the left, and 'Models' over 'Select a scope to view its models.' and an 'Enable Inspector' button below that. Yes, I checked the box on the 'Enable' tab.
None of it seems to do anything.
On the 'Models' tab, clicking 'Scope()' (per the instructions on the 'Help' tab) does nothing, nor does clicking anything else. Weirdly, under the Options tab, I can check Show applications, Show bindings and Show scopes, These make pretty (and pretty useless) boxes around sections of the script's resulting page, above the dev tools pane, but all the checks clear as soon as I click another tab, like 'Models' (where nothing is working, still), and then come back to the Options tab.
Says I'm on "1.0.2 debilitating-awesomeness"...which is the AngularJS version, I suppose, but really describes batarang so far.
PS: I watched the video (http://blog.angularjs.org/2012/07/introducing-angularjs-batarang.html) but it was useless, as it assumes the thing is already working.
Oh, yea, Win7Pro64SvPk1, Chrome 34.0.1847.131 m 'is up to date'
Hope the other recommended tools work better, or at least work.
Meanwhile, can anyone confirm the status of batarang? Sure seems a lot of people have a dead extension.
Try "AngularJS Batarang (Stable)" by "spencer.leland". It works for me.
I use AngularJS 1.3.6 and Chrome Ver. 39
The last release of Batarang was over 10 months ago. It looks like it is no longer supported and does not work with Angular 1.2.x
I can confirm that the stable version (https://chrome.google.com/webstore/detail/angularjs-batarang-stable, version 0.4.3) works fine, with Angular 1.3.13 and the Ionic framework.
On the "batarang stable" page they even warn that this version works and the newer version doesn't.
I tried the newer version (https://chrome.google.com/webstore/detail/angularjs-batarang, 0.7.4) and it didn't work indeed, half of the options were gone from the UI.
I had issues with Batarang while running a page as a file with the file:/// protocol. Putting things inside Nginx and running the page from that webserver solved my problem.
This probably applies to Apache and any other web server. I am running Batarang 0.8.6 on Chrome Version 45.0.2454.85 (64-bit).
So, Batarang IS working in the latest version.
Related
I'm trying to create a web application for university. I've been doing fine with XAMPP, using Visual Studio Code and Sublime Text as my editors and so far so good. However, a couple of days ago, I ran into what seemed to be a bug.
While accessing "localhost" on Chrome, the website didn't seem to reflect the last changes to the HTML and CSS code. I also modified some Javascript and it didn't work either, the website stayed the same.
Not even simple things like changing a colour on CSS or adding an alert window on Javascript would appear on the actual web.
Inspecting the website in Chrome shows the old documents and source code, however, when going to the "htdocs" folder at XAMPP, the documents were successfully changed, and no matter what I did, relaunching XAMPP or Chrome didn't fix it either.
I decided to give up for the day and committed the changes to my GitHub repository. To my surprise, I refreshed the website afterwards and it worked.
I thought it was an isolated bug, but it seems like it is not, it happened today again while working on a completely different project.
What's more surprising, this behaviour doesn't seem to happen on Firefox or even Safari, I've tried both and it seems to be fine. However, I prefer the tools included in Chrome, so I'd rather use this one.
Has anyone else had the same issue? If so, how did you fix it? Or in case it is intended to work like that, why is it? I don't see any possible scenario where this could be useful.
Thank you in advance.
This is more of a workaround than a solution really, but you could just try ctrl+F5, this will clear your cache and you're good to go again.
This is probably the single worst Chrome bug when you're doing incremental small changes but Chrome loads it from the cache and not the original files.
What does Ctrl+F5 do?
This ignores the page saved in the cache and does a fresh GET. This should serve well enough as any changes made will be reflected in Chrome on doing so. Or you can manually clear the cache from the Chrome settings.
I'm working on an ASP.NET app with Visual Studio.
The problem is that every time I launch the app, the IE has some css and js file cached so I have to manually clear the cache and only then run the app.
Added a external command in VS2012 that runs this tutorial but it runs only once and then it does nothing (I didn't check what triggers this one time).
I'm looking for either VS configuration, external tool, command line, anything that will let me clear the cache by a single click without the need to open the IE.
Thanks
OK, found a solution for my problem.
Don't know how I didn't see it before but the IE debugging window has a button for clearing the cache.
I couldn't find anything similar in Chrome (didn't look in FF and Safari) but for now I'm working only on IE so that's fine.
btw: I tried several other alternatives such as writing scripts/deleting registry entries but nothing worked. Some worked for the first time until next machine restart.
I hope someone can come up with a more efficient way.
I am working with ie6 (unfortunately) and i am having a javascript error. Its wondrous error message gives me a line in the html source, but unfortunately the javascript that does run changes the code for the page(dramatically). So the error that its pointing me to is a closing div tag, not actual code.
Is there a way to view the updated code for the page so I can at least know where my code is breaking?
I should also point out what im developing in.
I am developing a sharepoint 2007 solution for an winxp and ie6 user base. I am working via remote desktop on a sandbox winserver 2008 r2 and can access the site from my terminal. Now, unfortunately in my sandbox server i have ie 8 in which my code works. So im stuck on ideas. If anyone knows how to view the updated source on the page, i would be very grateful.
Thanks.
Edit. I should also mention i dont have admin access on my terminal. So i cant install visual studio. It would take a couple weeks for an issue ticket for temp admin access to install it, and this is sort of important.
If you can't install anything and the error console information isn't meaningful, then about all you can do is start modifying your code until you can find which section is causing the error. The kinds of modifications you can do are as follows:
Comment out a chunk of code in a way that won't cause more errors. If the error goes away, then you know it's in that block of code or something that code calls. Put that block back in and then comment out a piece of it and so on until you narrow down where the problem is.
Start inserting alert("1"), alert("2") prompts into your code with the goal of identifying which alert the error comes before and after until you've eventually tracked down where it is. When you rule out an area, remove the alerts to make it feasible to still run the app.
On a more modern computer (e.g. Vista/Win7) go to Microsoft's site and download both Microsoft Virtual PC and the Windows image for XP with IE6. You can then actually install things into the VM and do real IE6 debugging or at least see what the actual error is.
Find a computer with XP/IE6 on it that you can install real debugging tools on.
Build your own dummy little debug window using a textarea and a couple functions that append text to it. Put that into your browser page and start sprinkling mydebug("Entering function foo") statements throughout your code so you can narrow down which statements occur before and after the error and eventually find the error. This is how I've done some IE6 debugging when it was't worth the trouble of setting up a full-blown debug environment for IE6. This works much better than alerts for some types of problems because it doesn't interrupt the flow of the app or require lots of user intervention and you can scroll back through the history.
If you are using visual studio you can use it to debug js errors in ie.
Go to the Advanced Internet settings in ie and make sure that the two
Disable script debugging settings are turned off (so that script debugging is enabled)
and that the setting
display a notification on every script error is enabled.
If you don't have visual studio installed you can download and install microsofts script debugger (it's free just google it) and use that, tho it is not as easy to work with and won't give you as much useful information
Using the repo found here:
http://github.com/nkallen/screw-unit
and this commit:
cc41f3cf373d804b11519704faf1971370f43760
I get this screen when viewing the package's "EXAMPLE.html" file:
Basically all of the text showing how many tests were run and the describe/it clauses, and the test results are missing.
The same revision works fine on Safari and Firefox.
I found this report that seems related, but no follow-up:
http://groups.google.com/group/screw-unit/browse_thread/thread/f0e82f5d68acbf21
Any ideas?
Edit: I found that upgrading jquery from version 1.2.6 (included with package) to 1.4.2 results in a screen in which green/red tests show up. Unfortunately, the top header showing the number of total tests and failing tests does not show up.
For those who may be hitting the same problem, I've found that the Pivotal branch of Screw.Unit seems to give exactly the same output for EXAMPLE.html in both IE7 and FF. There are others to choose from as well.
Save yourself the trouble and use Jasmine. It runs on all browsers, offers custom matchers, works on all browsers, is offered by Pivotal Labs, and is wicked fast. Syntax is very close to Screw.Unit, so porting is not conceptually difficult.
Our website uses the superfish jQuery plug-in for our menus (http://users.tpg.com.au/j_birch/plugins/superfish/), and they work fine in Firefox, IE6, IE7, Safari, Chrome, etc. ... and even in MOST IE8 installations. The problem is, in some IE8 installations, the menus don't work (they highlight on mouseover but don't drop-down the menu).
This has me baffled. In addition to a couple customer complaints, I've got one (Windows XP) machine in-house that reproduces the issue. However, I also have another Win XP/IE8 machine in-house which doesn't experience the problem. I'm used to dealing with JS/CSS issues between different browsers, but this issue between two machines on the exact same OS and browser is a bit much.
Oh, and just to further obfuscate the matter, the machine that is reproducing the issue shows no errors, Javascript or otherwise (even when I go in to developer mode). So ... does anyone have any suggestions on what could be going on?
As far as I know neither of my two "test" machines have any special plug-ins or anything which would cause the problem, they're identical in terms of everything that matters, and there's no JS error occurring that I can check the stacktrace of or anything. But this isn't just some crazy problem that's unique to my test machine, because as I said some customers have reported it too.
Any help would be appreciated.
Can you try setting the IE7 compatibility mode and see whether the problem persists?
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
(into the head of the document, best would be directly after <head>)
If it works then, you'll definitely know that it is some IE8 specific rendering issue. My first bet would be that your menu uses CSS hacks to set certain IE specific settings, unaware that IE 8 (fortunately) behaves differently and more standards-compatibly than its predecessors. If that is the case, you would have to use an IE8 specific CSS hack (or, better, specific style sheet) to "re-fix" those settings.
But first, check whether this really is the problem using the compatibility view.
Try turning off compatibility view: Tools -> Compatibility View -> Uncheck. I too struggled with this for the better part of an afternoon until I just tried this on a whim and it worked!
Try clearing Internet Explorers cache. Go to Tools -> Internet Options -> Browsing History section -> Delete ... -> Temporary Internet Files -> Delete.
For reasons unbeknownst to me, I've seen all IE versions start behaving strangely when the cache has been full or not cleared for a long time.
I have a Windows 7 64bit Home premium. The laptop encountered an issue called SupperFish.
First I tried resetting home page to different URL’s. IE8 kept returning to SuperFish.com.
Look in Add and remove programs, was not there, Not in startup or MSCONFIG (startup).
Third cleared Cookies then History. No help. Forth ran Microsoft Security Essentials, SpyBot S&D, Norton Constant Guard , Ad Aware. Problem is still there, Looked in C:\Program Files and found a folder called SuperFish, in that folder there was an Uninstall executable. I ran the Uninstall using a administrator account, and the problem is no longer showing up, after several hours of use.
not sure if it is a solution and that this is what you meant by not knowing how to fix it... but I cleared all my cache/history/cookies etc. from IE8 and if immediately worked (looking the same as other browsers).
maybe a fix for now but that worked...
This issue wound up going away without us ever figuring out what caused it, so now even if we did want to figure it out we can't (as we can't replicate). Therefore I can't really mark any of the above answers as correct, but since they exist I can't delete this issue either. So, I guess the best I can do is file this answer, but it's a rather unsatisfying one; sorry.