Firewatch | - In case of fire

First thing first, I would suggest adding a position: relative; in the .parallax in order to remove the double scroll.

The issue you're experiencing is a browser related scrolling issue and not a problem with your code (it does work on Firefox, but not on Chrome for example). So there's no "fix".

But there's clearly other ways to go about using parallax to prevent the issue from even happening like scroll each parallax manually without relying on browser's scroll.

Or you can simulate a click when reaching the top or the bottom to be able to overcome the issue :

By adjusting the .parallax class I managed to get this result.

I removed the negative margin and set the left value to zero to expand the container to full-width.

It looks like it could be simplified quite a bit. Instead of looping over the device types and running a separate query for each one, you can just add the device type to your GROUP BY and get all your results in a single query.

I think CONCAT(YEAR(uptime_date),'-',MONTH(uptime_date),'-',DAY(uptime_date)) should output the same thing as date(uptime_date), and you should be able to use the aliases in your GROUP BY and ORDER BY clauses.

How about you loop through all the buttons on your page and add event listeners :

Steps

• Get all buttons on your page
• Loop through buttons collection
• While designing your HTML you can apply specific css class as an identifier on buttons you would like to add event listen to, use this check within loop.
• Define just one mouseover and mouseout functions to add and remove classes, attach them as event listener and pass class name via parameter (you may define these classes in some pattern i.e. buttonid + class )

sample code below

If you run anything from vim using :exec it is always on the terminal. Simplifying things a little it goes more or less like: when you spawn a command from vim, it switches to the terminal and calling terminal init sequence. What exactly the terminal init sequence means is encoded in terminal definition. For example, for xterm it means switch to buffer used previously and set the cursor in the last known position on this buffer. For screen it means: move cursor to the bottom line of the screen. That's why it gives you appearance of vim buffer. BTW, for other kind of terminal it could be clean the screen and move cursor to the top line. As I told - it's simplification. If you are interested about technical details, ncurses is the topic to read about.

So, in summary, vim always ask a terminal to do the same sequence of terminal command. If given command is known and executed by terminal, it depends on the terminal.

If you want to run something to get results inside vim buffer, you need to write a plugin to create a buffer and make it possible to interact between your command and a buffer. I wouldn't be surprised if someone have already written such extension but, also, I cannot guarantee it.

I checked this website a little tough. If you check link with using browser. You will see the loading... text. When you make the request actually you just get this piece of the page and the other data actually is not loaded. It was loaded by javascript. Maybe you can use selenium like solutions for this website.