My site works with all the browsers ive tested with except for IE7 (im not supporting IE6):
http://smartpeopletalkfast.co.uk/jquery2/new6.htm
With IE7 their is a weird > character appearing on the page:
Anyone have any ideas why this is happening? Its quite hard to debug as IE7 doesnt have the F12 feature of the newer browsers.
Thanks
The orphaned angle bracket is actually in your page source, between the second and third image.
There's a > in your source on line 177:
<div class="image-div" style="background-image:url('basicDemo_files/gnome.jpg'); width: 250px; "></div>
>
<div class="image-div"style="background-image:url('basicDemo_files/gnome.jpg'); width: 250px; "></div>
In most cases you can debug ie7 by using dev tools (F12) in ie8 or ie9 and selecting Internet Explorer 7 from the Browser Mode menu.
Related
The below is code of React
<QrReader
delay={300}
onError={this.handleError}
onScan={this.handleScan}
style={{ width: '100%' }}
/>
The link works fine on all Browsers in Android device, also works fine on Safari browser of iPhone devices, but it does not even ask camera permission for other Browsers like Chrome and Firefox on iPhone Devices.
The docs say Known Issues. On IOS 11 it is only supported on Safari and not on Chrome or Firefox due to Apple making the API not available to 3rd party browsers. See https://www.npmjs.com/package/react-qr-reader
I am using ui.router in my angular application with <div ui-view=""> </div>.
Everything works fine on Google Chrome but it is completely empty on Internet Explorer.
Below is a picture showing the problem and comparison between Internet Explorer and Chrome.
I am new to Angular JS. I am trying to include profile.html within profiletest.html by using ng-include.
Given below is the code of my profiletest.html
profiletest.html
<body>
<div ng-app="guestProfileApp">
<div ng-controller="guestProfileController">
<button ng-click="getProfile(401)">Show Profile</button>
<ng-include ng-if="showProfile" src="'profile.html'"></ng-include>
</div>
</div>
When I am making changes to the profile.html code, the changes are not getting updated in when I refreshed the profiletest.html in browser.
You can deactivate the browser cache - In Chrome Dev Tools on the bottom right click on the gear and tick the option.
Disable cache (while DevTools is open)
In Firefox there is the same option in Debugger -> Settings -> Advanced Section
(Not sure if it works in firefox. Alot of people say it doesn't work for them)
Just upgraded my browser to Firefox 40 (released two days ago) and now I'm noticing that base64 CSS background images are no longer displaying. All other browsers, including older versions of Firefox load the images just fine.
In the console, I get the following error:
Content Security Policy: The page's settings blocked the loading of a resource at data:image/png;base64,iVBORw0KGgoAAAA ......... CuwAAAABJRU5ErkJggg== ("default-src *").
My CSS looks like this:
.image {
background-image: url("data:image/svg+xml;base64,iVBORw0KGgoAAAA .....");
}
I am using Angular and had included the ng-csp directive on the html tag, though removing that makes no difference.
The comment left by kba was the solution! Adding a Content-Security-Policy header with an img-src of "* data:" did the trick. The new Firefox does not include the data: protocol as a part of the *, so explicitly adding it was required.
I'm debuggin a mobile application using Chrome devtools, I can inspect the device, network tab, console tab, etc are working fine, I can see the batarang tab AngularJS, when I click Enable the page is reload on the chrome mobile tab but the batarang tab don't show any kind of information.
Do you have any idea?
(source: vpsnotas.com)
It appears as though Batarang hasn't been updated to be compatible with the latest versions of AngularJS. Appears to be a duplicate of: batarang Chrome extension for AngularJS appears broken
Does the console show any errors or anything? That would be the first place I would look, as it will normally point you in the right direction of the issue.
I recently ran into an issue with loading Batarang on an angular app that I know was previous working. The console was throwing an $injector:modulerr error and the issue turned out to be with the ng-strict-di directive on the ng-app. After removing the ng-strict-di directive from the ng-app, the Batarang extension works fine.