I have a 'silverlight RIA' app with a customized splash screen with an image.
Everything seems work fine on my client side.
The problem starts after I deploy it on the server. My image is not shown anymore!
First of all, I had problems with showing the splash screen. But, after I changed the property of 'splashscreen.xaml' to "content" it became OK! But still it doesn't show the image after deploy!
Any suggestions on what's wrong and how can that be corrected?
You should start the url of the image by ../
Related
I'm under the development progress of nextjs based application and found some fuzzy stuff that's giving bad experience..
I'm just here to ask you whether it's possible to cache pages on nextjs development mode.
Now the problem is that I'm getting white blank screen for some seconds everytime I reload any pages. Changing route works properly and doesn't come with blank white screen.
Only when I reload the page by pressing F5 or clicking reload button, it shows me blank white screen on all kinds of web browsers. I know I can set the background color of index.html which will overlays during page loading but I don't think it can be the final solution to fix blank white screen.
Are there any way to solve the issue ?
I have using angular-bootstrap-lightbox in my project . its working fine in all browser.
But issue in safari of window.
Image that display in open modal is get disappear after display.
I have attached screen shot.
Please ignore grammatically mistake.
Thanks.enter image description here
I'm having an issue only in Chrome where it seems that the download bar is interfering with my AngularJS app.
The process goes like this. I have a grid, using Ng-grid, on the page which displays around 3000 rows of data. I have a filter function that alters the filterText of the grid. All of this code works fine until after I've exported something and Chromes download bar pops up at the bottom of the page. My export function just takes whatever the user has highlighted from the grid and exports it to a csv file.
Once this is done, if the user tries to reset the filterText of the grid back to empty the page lags horribly, Chrome throws some error pop-ups, and will sometimes crash. There is no error in the console log and I have debugged and haven't found any errors thrown in there either.
The strange thing is that if you have Chrome open, and the download bar is already present then the above steps will work and the page will be fine. It only happens when the download bar first pops up on the page. If you filter the grid and then go to a different tab and download something, and the download bar pops up, then go back to the app tab and try and clear the filters it still freezes/lags.
I'm not sure what the problem is because all the code works fine if the download bar hasn't popped up or is already up before I export.
Still unsure what the root cause of the issue was, but by upgrading my ng-grid.js from 2.0.7 to 2.0.11 seems to have fixed the issue.
I have a site which uses a different menu for mobile devices than on the Desktop version using media queries. If I resize a desktop browser window to a mobile width and click the mobile navigation dropdown button and then resize the window back to desktop size, the mobile menu remains visible instead of changing back to display:none. Unfortunately this site is still in staging so I cannot show you a live example, but I was hoping someone could point me in the right direction of getting that DIV to become hidden again once the window is resized back to full screen.
Also, I realize that the chances of this scenario playing out in the real world are slim, but the client would like for it to be addressed anyway.
Thanks!
I figured out that it was javascript that was showing the DIV in the first place, not a media query, so I just added display:none to the div for the Desktop media query and the issue has gone away. Thanks!
I'm having a problem with IE7 when clicking on images that open up using the Lightbox 2 javascript image viewer. Instead of overlaying the image on the current page it opens the image into a separate page.
Not sure if this is an AJAX problem possibly ? Works fine in Firefox.
Anybody else come across this before ?
Your page is performing the fall-back behaviour you would expect in the following scenarios...
JavaScript is disabled
There is an error in the JavaScript that is creating the lightbox effect (look out for a very brief flash of the yellow error icon before the next page loads - or fire up some dev tools)
There is a JavaScript error on the page before the image is clicked, which has stopped execution of JavaScript on the page (look out for the yellow error icon in the status bar again!)
The only thing I can think of is that I have google toolbar amd McAfee security installed that may be blocking the overlay (????) but don't think that should make any difference.