We Keep Coding

The javascript of bootstrap v 4.3.1, is not working properly in firefox v 65.0.1, has anyone had this problem yet?

When accessing the bootstrap v 4.3.1 documentation in firefox v 65.0.1, I noticed that the javascript is not working properly, for example, the carousel component is not following its normal flow, which is to move to the next slide with the its transition animation, other components have the same problem. I noticed that in version 4.0.0 of bootstrap this problem does not occur. I recorded a video with the carousel example, follow the link:
https://youtu.be/ksT7KgZZXhY
I have a site with this version of bootstrap, which is not working because of this problem, and in other browsers it works normally and in the console does not present any problem, I do not know exactly if the problem is in firefox or javascript bootstrap, I tested in other machines with old versions of firefox and worked normally, but after updating firefox gave this problem again.

I've been able to solve the problem. What happens is that in the performance settings of my computer the "Animate controls and elements in Windows" option was cleared, I do not know if this is a bug, as this is the first time I see a windows customization setting influencing loading of a website, anyway I left the link of the video with the solution.
https://youtu.be/9NhlpJpKpuQ

Disabling Scrolling on iOS 12 - Tried and True Stack Overflow Solution Has To Execute Twice To Work

I'm having an issue disabling scrolling on iOS 12.0.1. There's an old post (4770025) outlining solutions on how to disable scrolling however the system won't let me add a comment to it explaining my iOS 12 issue. It says I must have a 50 reputation to do so. My only way to raise the issue is to ask a question.
Old Post:
The solution from the old post I'm using (the most popular solution w/634 votes) was penned by gblazex. His solution worked fine for me on iOS up through version 11. However last night when I upgraded to 12.0.1 it suddenly broke. gblazex's working demo that implements his solution also fails on iOS 12 (Safari, Chrome, FF). However, when playing around w/the demo I discovered that when I press the disable scrolling button twice it "magically" works, the scrolling is disabled.
gblazex's Working Demo:
output.jsbin.com/xatidu/4/
I'm wondering why a second run of the code is necessary to make it work? I also want everyone to know if they are running into this problem in production a temporary work-around would be to run the code a second time. I adjusted my code to run twice and it fixed my application's issues w/iOS 12.
Thanks!

Superslides CSS issue in Chrome - need CSS guru

I have the superslides jQuery plugin installed here - http://coolon.businesscatalyst.com/
But the text container in Chrome only displays the text on the first slide. But works fine in FF and Safari.
Here is a link to the Superslides plugin in action with the text container working fine in Chrome - http://nicinabox.com/superslides/
I've tried everything and can't get it to display. Any thoughts!?

It seems the problem is that your images have
webkit-backface-visibility: hidden;
Just remove it.

i was facing the same issue but than i replaced the jquery.superslides from the one i downloaded from http://archive.nicinabox.com/superslides/ and it got resolved. The bug has been fixed now in the updated version of it.

Why does firefox white out pages in codepen?

Background:
I'm creating my navigation bar for my portfolio in codepen.io
I've notice that everything works excellently in chrome; however, when testing the pen in firefox, after click of a li item of a navigation. The page errors out by filling the screen with white. I noticed a similar problem with this in other pens.
Reference Example:
return false example from a previous stack question
The remedy was in the js return false had to be present.
Question:
This example is different because I'm not using any javascript. Only html and css.
Why does firefox have this consistent problem in codepen? What do I need to know to understand why this problem occurs so that in future coding I can be knowledgeable of this firefox caveat entirely? Lastly, why doesn't this happen in chrome?
codepen example

After checking out your codepen, it's clear it's nothing to do with your code.
I've done a search and found this question which seems like a very bug to the one you've come across. Looks like there's already a BugZilla ticket open for this issue, but as of yet it's unresolved.

Problem with Chrome 12.0.742.100 and empty a/span positioning

For a site i made, http://crystalmurray.com, i have a simple little script to smooth scroll to local anchors and push the anchor to the history like it never happened. Recently my chrome updated to 12.0.742.100 and this stopped working, however, it worked fine in safari and firefox.
The obvious workaround for it is to add content to each empty anchor tag and hide it, whether manually or programmatically.
Heres an example and tester for it http://jsfiddle.net/arzynik/zfmgt/
Both empty a and empty span tags fail to position correctly.
Any other suggestions? Id rather keep editing to a minimum when updating other sites.

Your test seems to work in Chrome 14.0.794.0 (canary). The problem is probably already solved in a future version. You can wait Or file a bug report.

I encountered this same issue recently. My workaround for Chrome 12 was to set position: relative for any empty anchor tags I had. The following should fix you up:
a:empty {
position:relative;
}