emphatic | online documentation

for s in username is iterating through the username by character. Therefore what you are essentially doing is:

is test in r?

is test in o?

do this instead:

You should set the background color to the pseudo-elements before and after like this

It looks like it's trying to fill in some area with the current background color, but where the "clip bounds" are supposed to be, and why that wouldn't be happening already, is outside my experience. Searching the rest of the source file for "clip" yielded nothing.

The "clip" is actually defined by the Graphics context and in most cases it is defined to the size of the component bounds anyway, although it can be used to increase the speed of painting in some scenarios, I wouldn't see a great deal of benefit for it here without more context

You can have a look at Painting in AWT and Swing for more details

The code is fairly old -- written in the days of Java 1.5

I've been writing in Swing since 1.3 and never found the need to do anything like this

Since one of the jobs of paintComponent is to typically paint the background, and in the case of a text based component, the text, the code seems to be doing, well, nothing.

have found a lot of their old code to be cargo-cult-esque, in that they've copied it in from some random project elsewhere in the company, so this might be more of the same.

This is probably a good assessment, it might have been used for trying to display placeholder text at some point and has been modified down to what you see now ... as a wild guess.

I think it's safe to say you can remove it without out any side effects

If you can't use callbacks, then use promises, which are designed to create a "blocking" mechanism in an asynchronous environment without having to add a separate callback function.

You don't need to add !important to change color, you can target the inner children, by targeting them using a custom parent class(.hamburger class here).

Doing this will override the hamburger.css, without using important class and also keep ur code clean

After consulting various online sources I have made the following changes in my function. So now it incrementally writes the output from the loop.

The general highlighter can't be toggled to stay on the page, it only reacts on hovering the nodes.

Only some other highlighters are sticky, like the one for elements matching a specific CSS selector or the CSS grid highlighter, both located within the Rules side panel:

The CSS selector matching highlighter is currently (as of Firefox 53) the one that comes nearest to what you're looking for, though it's missing the grid lines.

Furthermore, there is already a request for adding a sticky element highlighter in Mozilla's bug tracker.

Given that one element is not the parent of another element, you will have to pull up the variable keeping the toggle information up the chain of elements until it resides in one common place.

That is, keep the "active" state variable in an ancestor of the two elements and provide to the Hamburger a callback in the props that, when called, modifies the state of that ancestor component. At the same time, also pass the active state variable down to the MenuOverlay as a prop, and everything should work together.

See here for more information:

https://facebook.github.io/react/tutorial/tutorial.html#lifting-state-up

Specifically,

When you want to aggregate data from multiple children or to have two child components communicate with each other, move the state upwards so that it lives in the parent component. The parent can then pass the state back down to the children via props, so that the child components are always in sync with each other and with the parent.