As I've stated previously, I used the "Fluid width" setting in the customiser button on the top bar to maximise the width of the display to view AN content.

 

 

However it would appear that these settings are not persistent, even though I select save after enabling the "Fuild width" setting.

If I shut my browser down and reopen it, the setting goes back to "not set". Is this a defect or a feature?

It's not the end of the world if I have to keep setting it each time.

18 hours ago, Mutt Daeng said:

...If I shut my browser down and reopen it...

 

I'm not sure but I think it might help if you mentioned the names of the browser snd the device you are using.

 

It has been my experience that not all browsers display a web the same way and that the display may different from one type of device vice to another.

For example, I don't have the same problem on my device with the browser I am using.

2 hours ago, Puccini said:

 

I'm not sure but I think it might help if you mentioned the names of the browser snd the device you are using.

 

It has been my experience that not all browsers display a web the same way and that the display may different from one type of device vice to another.

I'm using Iron browser under Win 11 on a PC.

I'm aware that different browsers can behave differently when displaying the "same" webpage. 

Not sure how this is relevant since it is an AseanNow setting which is being unset and not a browser setting.

It's not the fact that the page is displayed differently, it's the fact that the AseanNow setting is being "unset"

1 hour ago, Puccini said:

For example, I don't have the same problem on my device with the browser I am using.

It would be useful if you mentioned the browser you are using and the type of device. 😉

4 hours ago, Mutt Daeng said:

It would be useful if you mentioned the browser you are using and the type of device. 😉

I made that post as an example to illustrate how difficult or impossible your opening post makes it for members to understand your problem and give helpful advice.

 

To answer your question about the device and browser I use, it is exactly the same you use: unamed device and unnamed browser.

 

Don't you understand? What help is it to you if 100 members post that they have the same problem or that they don't have the same problem and specify their device and browser but none of these configurations are identical to yours?

 

6 hours ago, Puccini said:

I made that post as an example to illustrate how difficult or impossible your opening post makes it for members to understand your problem and give helpful advice.

 

To answer your question about the device and browser I use, it is exactly the same you use: unamed device and unnamed browser.

 

Don't you understand? What help is it to you if 100 members post that they have the same problem or that they don't have the same problem and specify their device and browser but none of these configurations are identical to yours?

 

Thanks, I do understand and I agree with you that to better diagnose an issue it is important to have as much info as possible regarding the issue to get better quality suggestions to solve the issue. My bad.

I have the same problem using Brave on Linux Mint on my PC.

Just a bit annoying having to reset every time.  Cookies are white-listed so that is not the cause of the problem.

On 11/12/2024 at 8:55 AM, Mutt Daeng said:

As I've stated previously, I used the "Fluid width" setting in the customiser button on the top bar to maximise the width of the display to view AN content.

 

 

However it would appear that these settings are not persistent, even though I select save after enabling the "Fuild width" setting.

If I shut my browser down and reopen it, the setting goes back to "not set". Is this a defect or a feature?

It's not the end of the world if I have to keep setting it each time.

It now appears that the "Fluid Width" is now persistent. I no longer have to set it each time after logging off/on or rebooting. Thanks.

This topic can now be closed.

The OP has resolved this issue and I locked the topic.