(Observation) more fun with FireFox and Chrome display of web pages

While playing with CSS and stuff, I found another disparity between FF and Chrome on how they display web pages.

Two CSS buttons.

[{"id":"8d09f358.cc5c4","type":"ui_template","z":"1d85b106.5dfcd7","group":"2452ebe2.f30164","name":"Up","order":5,"width":"2","height":"1","format":"<button ng-mousedown=\"send({payload: 'down'})\" ng-mouseup=\"send({payload: 'up'})\"><i class=\"material-icons\"> volume_up </i></button>\n","storeOutMessages":true,"fwdInMessages":true,"templateScope":"local","x":140,"y":180,"wires":[["26653ac7.751afe"]]},{"id":"1cf491d1.c1c4fe","type":"ui_template","z":"1d85b106.5dfcd7","group":"b4f878dc.dd30f","name":"Up","order":5,"width":"2","height":"1","format":"\n<style>\n.button {\n  background-color: #097479;\n  border: none;\n  color: white;\n  padding: 15px 32px;\n  text-align: center;\n  text-decoration: none;\n  display: inline-block;\n  font-size: 16px;\n  margin: 4px 2px;\n  cursor: pointer;\n  \n  box-shadow: none !important;\n  width: 100% !important;\n  height: 100% !important;\n  margin: 0px !important;\n  min-width: 0px !important;\n  min-height: 0px !important;\n  white-space: nowrap;\n  text-transform: uppercase;\n  font-weight: 500;\n  font-size: 14px;\n  \n  transition: background-color 0.1s;\n\n}\n\nbutton:hover {\n  background-color: #0b8f95;\n}\n\nbutton:active {\n  background-color: #ff0000;\n}\n\n</style>\n<button ng-mousedown=\"send({payload: 'down'})\" ng-mouseup=\"send({payload: 'up'})\"><i class=\"material-icons\"> volume_up </i></button>\n","storeOutMessages":true,"fwdInMessages":true,"templateScope":"local","x":170,"y":510,"wires":[["14dc521f.fb0b1e"]]},{"id":"2452ebe2.f30164","type":"ui_group","z":"","name":"Audio","tab":"39b306a2.96619a","order":1,"disp":true,"width":"5","collapse":false},{"id":"b4f878dc.dd30f","type":"ui_group","z":"","name":"Audio2","tab":"39b306a2.96619a","order":2,"disp":true,"width":"5","collapse":false},{"id":"39b306a2.96619a","type":"ui_tab","z":"","name":"TV remote control","icon":"dashboard","order":45,"disabled":false,"hidden":false}]

Though there are 3 in the screen shots, take it as the first one is done twice for the up/down and the second one is all by itself on the web page.
Audio and Audio2

FF - after a refresh and deploy. No buttons pressed.

Screenshot from 2020-03-03 08-14-03

After pressing a button:

Screenshot from 2020-03-03 08-14-08

See how it changes size.

Chrome: no change.

Now the first button pressed.

Screenshot from 2020-03-03 08-14-15

(Though it is the "second" button.)
That is the first button of the code I posted.

Ok, this is getting confusing in what I am saying. I just got up.
Thing is: There seems to be a bug with how FF displays buttons with CSS, compared to Chrome.

This is probably of no use to anyone, but just to get it out there of this observed problem.
It sort of had me thinking I was going nuts (more than I already am) with what I was seeing.
Buttons changing size.

Make sure that caching has been turned off.


Can I disable caching for specific IP addresses?
(Semi rhetorical)

You turn it off for the browser, not ip.


I meant turning it off in the browser for a specific IP rather than a general turn off.

You turn it off for the browser, not ip.
See google.

Both Chrome and Firefox have an option to disable the HTTP cache while the developer tools are open. It's hidden in the dev tool's settings after you opened them. Search for "Disable HTTP cache (when toolbox is open)".

Really useful, and you don't need to disable it globally that way.


As I was researching this (again) I remember that if I use PRIVATE BROWSING, caching is not going to happen.

In private browsing (FF) the buttons still change size.

(More work to be done here when I get time)

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.