Looking at the Scientific Paper example from README.md, there are at least two selectors that are case sensitive, .Bi and .bi:
.Bi {
position:absolute;
border:0;
margin:0;
top:0;
bottom:0;
width:100%;
height:100%;
-ms-user-select:none;
-moz-user-select:none;
-webkit-user-select:none;
user-select:none;
}
.bi {
position:absolute;
border:0;
margin:0;
-ms-user-select:none;
-moz-user-select:none;
-webkit-user-select:none;
user-select:none;
}
According to the standard, however, CSS should be case insensitive. Although browsers often treat class names as case-sensitive (because HTML attribute values are case sensitive), that is not always the case. For example, if the CSS is injected into the page via JavaScript the selectors (even those for class names) are treated as case insensitive.
In the specific example above, if the pdf2htmlEX output is rendered without CSS case sensitivity, the background image for figure 1 receives the properties of both the .Bi and the .bi classes, and is (incorrectly) absolutely positioned at the top of the container, as can be seen from the screen shot below:

Looking at the Scientific Paper example from README.md, there are at least two selectors that are case sensitive,
.Biand.bi:According to the standard, however, CSS should be case insensitive. Although browsers often treat class names as case-sensitive (because HTML attribute values are case sensitive), that is not always the case. For example, if the CSS is injected into the page via JavaScript the selectors (even those for class names) are treated as case insensitive.
In the specific example above, if the pdf2htmlEX output is rendered without CSS case sensitivity, the background image for figure 1 receives the properties of both the
.Biand the.biclasses, and is (incorrectly) absolutely positioned at the top of the container, as can be seen from the screen shot below: