CTS
Rookie Contributor
Edit to add: XF 2.3 OEM style
I recall back in the day where you had to make sure your site looked the same on Explorer, Netscape, Opera, etc. And you did because there was always that something.
I learned something today while styling my new website.
I opted for the dark oem templates and style properties. Had it kinda looking good on Chrome, which is my primary. Today I had a need to view it in Edge.
Low and behold, Chrome will remember dark styling as a guest vistor, but Edge defaults to XF Light.
I know now that xf default dark is not the default style fed to the guest visitor. It is default light, even if you have dark set for all usergroups.
I didnt know this because because chrome decided to remember, and didnt give me a clue.
But Edge clued me in. I did have to install a tiny addon and adjust style settings to make it work tho.
Andy has an addon to force dark default to guests. I also changed the default style to unselectable. That will produce an error but it will stick. Verified step by step on Edge and Chrome.
Anybody else run into this? What were your solutions?
I recall back in the day where you had to make sure your site looked the same on Explorer, Netscape, Opera, etc. And you did because there was always that something.
I learned something today while styling my new website.
I opted for the dark oem templates and style properties. Had it kinda looking good on Chrome, which is my primary. Today I had a need to view it in Edge.
Low and behold, Chrome will remember dark styling as a guest vistor, but Edge defaults to XF Light.
I know now that xf default dark is not the default style fed to the guest visitor. It is default light, even if you have dark set for all usergroups.
I didnt know this because because chrome decided to remember, and didnt give me a clue.
But Edge clued me in. I did have to install a tiny addon and adjust style settings to make it work tho.
Andy has an addon to force dark default to guests. I also changed the default style to unselectable. That will produce an error but it will stick. Verified step by step on Edge and Chrome.
Anybody else run into this? What were your solutions?
Last edited: