Developer Tools mastery is a vital part of my front-end toolkit. Even when you have the source code, there’s nothing better for learning how something works and debugging than being able to change things in real-time without reloading a page. Learn to love this stuff and it will love you back.
Modern browsers have Developer Tools. Safari may need toggling on and off.
Safari instructions for Developer Tools
Firefox, Chrome and Edge, I typically just right click on an element.
The 4-second limit seems long enough that I might just race against the clock, but if that doesn’t appeal to you, try event listener breakpoints which should work in Chrome and Edge, or Event Breakpoints in Firefox.
Once you see your modal pop up, you can right click on it and inspect that element in Developer Tools. It should then be trivial to find the element’s style and edit it to remove those values you don’t want.
You can then save the output style you’ve changed directly, removing the need for source code entirely. Chrome/Edge has a tool, while Firefox users tend to just copy/paste.
Extra Thoughts on Frameworks and Event Manipulation
It sounds like you may be inspecting a website with a framework as fadeIn/fadeOut
classes only do things if they’re told to.
If that’s the case, you have lots of options. If you only care about the modals being visible then simply removing display: none;
from fadeOut
should work fine. Otherwise, you may want to step into the Developer Console and remove the event with JavaScript. I’d probably pair that with directly editing the modal to make it always display, or add a new event listener that adds display: block;
or fadeIn
without the corresponding timeOut
call to fadeOut
.
If you don’t care about breaking the overall functionality of fadeOut
, removing the display
attribute should work fine though.