You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding a Chanu widget to the home screen, it will usually use the board title (which for some reason is always /a/) even if it shouldn't, and show the refresh and settings buttons even if they shouldn't (though it still uses images from the correct board). This can rarely be worked around by adding a widget with the default settings (/a/, show board title, show refresh button, show configure button) and changing the settings, though it's unpredictable and will eventually revert to showing the title (which is always /a/) and buttons, however it will continue showing images from the custom board despite the title invariably saying /a/. Additionally, once it "reverts" (which happens the instant the widget is created unless I'm really lucky), the "configure" button ceases to work, opening Chanu instead (perhaps it's displayed but not actually there?).
The text was updated successfully, but these errors were encountered:
When adding a Chanu widget to the home screen, it will usually use the board title (which for some reason is always /a/) even if it shouldn't, and show the refresh and settings buttons even if they shouldn't (though it still uses images from the correct board). This can rarely be worked around by adding a widget with the default settings (/a/, show board title, show refresh button, show configure button) and changing the settings, though it's unpredictable and will eventually revert to showing the title (which is always /a/) and buttons, however it will continue showing images from the custom board despite the title invariably saying /a/. Additionally, once it "reverts" (which happens the instant the widget is created unless I'm really lucky), the "configure" button ceases to work, opening Chanu instead (perhaps it's displayed but not actually there?).
The text was updated successfully, but these errors were encountered: