I have a Ransack search and Foundation in my Rails app and locally css renders ok while the same app in production has a quirk:
other things in the app are exactly the same.
I tested in Chrome and Safari - locally ok, production not ok.
Where can I start troubleshooting this?
UPDATE: I tried to run in production locally (assets:precompile) and it's the same as on the server... so how come asset compilation can change something?
One of the sites probably has a global css selector that set the margin or padding (can't really tell from your example).
Go to the production site and inspect one of the elements. You should see a difference in its computed style.
Related
While using Next.js + Tailwind + DaisyUI in development on Mac everything works as expected and all styles look normal, however when developing on WSL I noticed that my styles look very different and are pretty much broken from what I would expect. I'm encountering this same issue when deploying my site to Vercel. Does anyone know how I can resolve this?
Development (Mac)
Deployment (Vercel)
tailwind.config.js
I attempted to recreate the issue on my mac with no luck, however it seems this issue is showing up on Linux and Vercel deployment.
Update:
Turns out the issue stemmed from the fact that I had a css file in my styles folder and when I imported it into my homepage, it messed up the styling for everything else.
Not sure if this is supposed to be the expected behavior, but it did solve the issue
In my local development environment, everything works as I intended. However in after running yarn build all of my styles are way different. I used create-react-app to set up the project, and I am using regular CSS to style it.
here is my file structure
and here is an example of what I am talking about.
and here
turns out there was nothing wrong with my code I was just zoomed in 500% so embarrassing
after upgrading Angular from version 8 to 11, fonts are looking different, they are blurred. Any ideas what can I do/check to make them look the same as they were before? Any help would be appreciated. When I run app locally, it looks better than on deployment environment.
You might be hit by something similar to this issue.
There is a new optimization for fonts - external font definitions are inlined as part of the production build. According to the bug above, it might not work in some cases.
Try disabling the fonts inlining optimization in angular.json - https://angular.io/guide/workspace-config#fonts-optimization-options
I build a web app using Vue.js2 and Sass packed with webpack, transpiled with Babel. The backend is build with PHP framework Symfony2.
I have full support for browsers based on webkit - Chrome, Opera, Firefox, Edge, however, I did everything to make sure it's compatible with IE11, I have some issues on production and testing env (both run under apache2). CSS are autoprefixed by webpack plugin and PostCSS.
While I run the server locally using PHP built-in server, everything works perfectly. While I launch the app from server with apache, in Webkit browsers, everything works perfectly as well. Now the interesting part is, IE 11 is not able to load complete asset files. CSS are broken and barely half of the page is styled up. Also the Javascripts are incomplete, that causes missing fc declaration and nothing is rendered due to errors.
This occurs only in IE11. We have F5 firewall on production, also internal proxy in our company's network. But since the problem is only IE11 related, I don't think the problem lays there.
Do you have any idea, where's the problem? Can apache modify headers to be incompatible with IE11?
Ok, so here is the issue we are having. We have a website that uses a DevExpress callback panel. We have gotten calls from users using IE10 that the page is blank.
I setup a machine with IE10 - to try and replicate the problem. When logging into the production website, I saw the same thing – the page is blank, except that you can see an empty SpitterControl up in the top left corner (indicating a control with nothing in it). I checked the f12 developer tools, all of the markup is there. Also, when going to quirks mode, or IE9 mode, page renders fine.
So good so far. The next step is to replicate the issue in my local environment so I can throw in some breakpoints and try to find the cause. Here is where I am stumped. Local dev environment no issue at all; Page renders fine in IE10. I am running IIS7 on my machine with the same .NET framework.
So, on to the next step. We have a machine where we stage code for beta testing – its configuration basically mirrors the production configuration. Same result, all IE10 pages rendered just fine.
I have kind of run out of ideas. I have of course researched the doctype, and forcing the IE9 mode. All things that I could try, but I just puzzled by the fact that all of my testing environments I could not get it to break.
Any thoughts?
Try setting up an offsite dev setup. It could be that within your domain. I know that in one case we had problems with devexpress controls loading out of order.
Figured it out - well work around anyways. Setting the worked. It just wasn't so simple to just make a change like that to the production database - but I finally got it in there to try it. Jeez.. what a pain!
The NuGet package option from this link worked for me so I assume that installing the hotfix on the server would also work:
http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
SUMMARY:
Make sure you have NuGet installed
Right click on project then click on Manage NuGet packages
Search Online for "App_BrowsersUpdate"
I installed the one for .net 4
Republish