We have a very old application running that has stopped printing correctly when users hit it with IE11. Displaying on the screen works, but when you print the page the content of all the dropdown boxes disappears as well as the little dropdown box arrows.
Works in FF and Chrome and IE10 or smaller just fine
On Screen it looks like this:
But the Print Preview in IE11 looks like this:
And it prints this way too. No down arrow graphic and no text in the dropdown.
The page is using a print.css.
Thought I would ask if anyone had seen this behavior before I started posting source code.
Thanks!
Related
I am using CSS "backdrop-filter: blur" on a <ul> element, to create blurry background. However, on my PC the blur doesn't look as it should.
This is the expected behavior from a design template.
This is what i get on PC with "backdrop-filter: blur(15px). The text also gets a little bit blurred.
This is what i get with blur(30px). The text isn't blurred anymore, but the background looks even worse.
I've tried to open the webpage on my phone, and the filter works fine - the background is evenly blurred as in the design template, the text also appears correct. On my PC i've tried to open it with Chrome (Version 104.0.5112.81) and Opera, and it looks identically bad. I'm also using Windows 7 and didn't get updates in a long time (it's not supported anymore) - could this be the problem?
So This is my problem https://imgur.com/a/I8NR9VU You can see what it should look like and what it actually looks like. It lloks fine on mobile safari? I even develop on chrome, so why doesn't it look like it should. It's not centered it doesn't have padding? Even though its written in the css? Also to view the dialog box you need to submit the forem in the footer. here's my code
https://github.com/spabsa/Chapman-Automotive-Skills-Assessment
I have encountered an issue in select element(Combox box) in the chrome browser, whereas it looks okay in firefox. you can see attached image here.
when i hover in select option the text won't come vertically middle.I haven't posted any code part here because i could not re-generate it on fiddle.
Please go through this link below on chrome browser and See field Type of Enquery http://organic.draftserver.com/index.php/contacts
I'm using a Google CSE on http://afv.com and the results page is so wonky for Firefox and Safari. Here's what I see:
Chrome (looks perfect):
Firefox (magnifying glass gone in blue button, text falls out bottom of input field):
Safari (input field far too wide, sends blue button off edge of page):
I've mucked around with the style sheet Google gives me, to try to override some styles and standardize the output, but I can't see why it's so weird across browsers. Any thoughts? I know using a CSE is a bit of a hack and I'm having to shoehorn it into my layout, but these pictures show some incorrect layouts (or in the case of Safari, wildly incorrect), beyond just minor formatting issues.
This is probably because some of your own css is influencing the search button (e.g. a library like bootstrap or a css reset). If you try a search button without any additional styles - e.g. this one:
enter code herehttp://jsfiddle.net/buQL3/1/show_html/
it should render correctly (renders well for me in OS X 10.8.5 latest Chrome, Firefox 24 and Safari 6.0.5).
After months of working correctly, the large version of the Facebook Like button has stopped displaying the number of "Likes". The compact version works correctly, but the big button hides the number. I am on a Mac, and the buggy behavior is consistent on Chrome, Firefox and Safari. You can see the big buttons NOT working on JoomlaDigger.com, and you can see all the small buttons working correctly on each article view.
After digging into the markup, the div with class "connect_widget_number_cloud" has element style "visibility:hidden". Very strange, since the markup does NOT show this CSS style, but Chrome CSS Inspector shows the element style.
This bug appeared on September 1st, 2011. Can anybody from Facebook comment on this?
It is also currently broken on Facebooks own page. And the bug has already been filed.