I have an ASP.NET 1.1 app that does not work in IE10. When I try to navigate anywhere, I get a blank screen. The html of the blank screen looks like this:
<asp_smartnav_rdir url="/MyWebFormName.aspx"/>
I have seen the fixes for what sounds like a similar issue for .NET 2 through 4, but there is no App_Browsers folder in .NET 1.1.
The workaround that I settled on for this issue is to simply disable smart navigation. I wasn't using those features anyway. I'm not sure why it's broken in IE10 and not other browsers, but I can live without it.
I disabled it by setting smartNavigation="False" in the #Page directive of my aspx pages. It can also be programmatically set in the aspx.cs file by overriding the OnInit method and setting this.SmartNavigation = false.
Related
I have recently created a Blazor Server application and added the Admin LTE ui. Everything on the ui works as planned except the data grid with the buttons found here:
https://adminlte.io/themes/v3/iframe.html
In Blazor I have added all the js files and the stylesheets as per the downloaded page on github.
https://github.com/ColorlibHQ/AdminLTE/releases/tag/v3.1.0
Here is the problem, when I load the page the buttons appear for a brief moment and then disappear again:
Not at all sure why this happens. When I click fast enough the buttons does work it just does not stay there
I have a PWA (specifically concerned about iOS Safari at the moment), where when I add the PWA to my homescreen, the page I was on when I added it shows up like a native app. However, when I navigate within the PWA (same domain just new pages) the URL bar shows up.
This post was similar, but mentions it's for chrome/android.
PWA: Address bar showing up when redirectioning to subdomains -- and, as I understand it, iOS doesn't use all of the manifest file. I tried setting the scope, but no luck.
I have the necessary head elements in for showing a standalone (like I said, the initial page when I saved the PWA to the homescreen works fine).
Any ideas how to fix this?
I was able to resolve this by undoing the router mode history and reverted back to # hash-based routing.
I'm using Vue, so basically I just undo what I did here
https://router.vuejs.org/guide/essentials/history-mode.html
I have created an extension and added to a page when I executed page got a blank page. Then I inspected through view-source of browser the contents are there. but not visible.
The view was visible on Typo3 v7 local, but not on the server.
I'm using the Typo3 v7 and Typo3 v8.
Extension has been installed in both server versions, but not displaying.
I have included the extension into the template.
I have Checked the Debug functionality through the controller
that also didn't display on front-end, But is visible as source code
Should anything to be done more? Any idea?
Thank you
That does not sound like a problem of TYPO3 than a problem with CSS.
If the HTML markup is available at the browser but not visible the browser has decided not to show it. And that probably is CSS. Use the browser debugger (firebug, inspector, ...) to identify which CSS hides the content.
Also Javascript might interact as it could change visibility after page submit. (try to load the page with deactivated javascript)
In the end it could be an additional or missing div tag or css class that is responsible and you could configure TYPO3 to change the HTML markup in the way so that your content is not hidden.
If you have one server where the content is visible and one where it is not shown you may do a diff on a page to find the difference between these servers. The HTML could be the same if CSS and/or Javascript is different.
I would save the same page from both servers localy (with all CSS and JS) and do a tree diff with a tool like kdiff3
Is there a way to live edit ASP.NET in VS2012 the way that you can live edit AngularJS in WebStorm? I saw and installed AutoF5 but the project seems to have been abandoned and isn't working anymore.
I'm currently working with the AngularJS SPA Template and would like to see my changes as I'm learning AngularJS.
P.S. the only view I have in my document is source. And even if I could actually see what it looked like, it still wouldn't be what the user would see when the page is rendered.
There is the Browser Inspector in Visual Studio. You can edit and see as you go...
When I currently try I get the following error, even after adding google as a content URI
APPHOST9613: The App Host was unable to navigate to http://www.google.com/ due to the following error: FORBIDFRAMING.
Response from MSFT:
http://social.msdn.microsoft.com/Forums/en-US/winappswithhtml5/thread/a1cba639-3251-4df8-abd3-b6f6a95ba4ae
You can use Iframe,but you won't get full controll of their JS files,you may have to face some breaking point in such sites, and some sites like google blocking this facility.
Try this,
1. Make your default browser as IE10 which will provide you an App look for IE.
2. trigger an event
function openYourLink() {
var url = new Windows.Foundation.Uri("http://www.google.com")
Windows.System.Launcher.launchUriAsync(url);
}
You can use iframe to navigate to other pages.
<iframe src="http://www.apple.com" />
will do the trick.
However, not every website allows you to put their page in an iframe or they maybe using the top window layer so that their page doesn't support running in an iframe.
In addition, if you are running your code Visual Studio 11 Express, it may throw javascript exceptions in the web page in the iframe. You can "continue" it. This exception will not be visible when you are running a deployed version of your application (running from start menu).
On further investigation the answer seem to be that yes you can for most sites, but some sites (such as google) seem to fail when embedding with an iframe.