Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Why is FireFox doing this to my web page, why is it ignoring styles and style sheets?

more options

There are two images here the one in green is Firefox the other in Chrome.

One of these is loading correctly and one is trashing the image layout.

It is something that Firefox is doing to the images...

CSS and or Styles tell Firefox what to do and Firefox is not doing it???

What can I do to render these in Firefox the way Chrome renders them?

There are two images here the one in green is Firefox the other in Chrome. One of these is loading correctly and one is trashing the image layout. It is something that Firefox is doing to the images... CSS and or Styles tell Firefox what to do and Firefox is not doing it??? What can I do to render these in Firefox the way Chrome renders them?
Đính kèm ảnh chụp màn hình

Giải pháp được chọn

It took me a while to see it. This problem is caused by a slight font size difference between Firefox and your other reference browsers. The slightly wider width of the wording under 86it Community causes the table to be a bit too large and because you apply table-layout: auto, Firefox makes space by moving the content to the left. If you change .table100 to table-layout: fixed that resolves the issue:

Đọc câu trả lời này trong ngữ cảnh 👍 2

Tất cả các câu trả lời (7)

more options

you can reproduce the error by looking at PHP-Nuke Titanium at https://www.php-nuke-titanium.86it.us

Thanks in Advance.. I spent hours making this theme so that my buddy could access it with Firefox

more options

Is anyone looking at this or does anyone care?

more options

The thing I noticed, which I assume is what you are referring to, is the animated background behind the content. Actually, it's a video and in other browsers, it auto-plays, while in Firefox, it may be blocked by the autoplay block. You'll notice an extra icon next to the lock icon in the address bar when autoplay is blocked:

Click that icon to open a panel where you can change the permission. Note that it won't take effect until you reload the page (either click the Reload button on the toolbar or press Ctrl+R). Then you can enjoy that totally annoying animation in Firefox, too. See attached screenshot comparison.

Ref. Allow or block media autoplay in Firefox

more options

If you were referring to some other difference between the images, what is the difference, I can't see it.

more options

The images are not lining up where they should be. In the left side block. look closer... Visit the page... https://www.php-nuke-titanium.86it.us

Once you are on the page you will see that where it says 86it Community under the Portal Menu on the left side of the page, the icons are messed up. Images and the CSS are not lining up in Firefox. And no there are no other browsers with this problem. A function creates the menu so all the other links were made by the same function and all display properly on every single other browser in production. There is no error in the CSS or the function; Hint the function ran and created all the other menu links correctly. I assume FireFox is seeing a number in the string and doing something it should not do with it. THE ONLY THING DIFFERENT IN THE STRING VALUE IS THE NUMBER 86...

When CSS tells the browser what to do it needs to do it correctly.

more options

By the way, if you want to see how it is supposed to be displayed load any other browser. Thanks

more options

Giải pháp được chọn

It took me a while to see it. This problem is caused by a slight font size difference between Firefox and your other reference browsers. The slightly wider width of the wording under 86it Community causes the table to be a bit too large and because you apply table-layout: auto, Firefox makes space by moving the content to the left. If you change .table100 to table-layout: fixed that resolves the issue: