Should be used whenever you activate the "download_remote_images_to_local" site setting to prevent users from receiving a lot of edit notifications from the system user.
Add a new SiteSetting to specify a maximum of items to be shown in post action menus per default. If more buttons are rendered and those after mentioned maximum will be hidden behind a collapsible ellipsis-button. Once clicked it slides in the missing buttons and hides itself.
If the setting is set to 0, the ellipsis will not be applied. It default is set to 4 though.
All buttons are created equal - but the Reply-Button is more equal than others: If it is rendered, the reply button will never be hidden behind the ellipsis. The max count is exclusiding the reply button and its position would make the reply button hide, it is removed there and pushed to the end of the list.
I upped the slack ratio for a few reasons
1. We render ucloaked anyway on first render,
so cloaking really is not saving much
2. On mobile you don't get JS events so you need
a lot more slack to minimize white screens
3. Vast majority of memory is used by object model,
if we want to tame it we need to remove posts from stream
ember cloaking now supports high slack ratios without going into a tail spin
The notifications panel would reset itself
if you got a notification while it was open
New behavior, we refresh the panel live, blue notification
is cleared automatically if its open.
If window is not visible it will close the notifications panel,
that way you don't miss notifications by accident.
There were 2 issues:
1. We were resetting our tracking on large amounts of idle time
2. We used focus trakcing which is fragile and broken on iPad vs page visibility API
Use "Site Name <>" for the Reply-To header when the reply is to the site or a public topic.
Use "username <>" for the Reply-To header only when the reply is to a private message topic.
