dw_maintenance | (no subject)

Tonight's code push is now complete! As always, please report any issues here.

(We're particularly interested in issues with HTTPS browsing; we're getting closer to ironing out all the bugs, but we know it's still not perfect.)

EDIT: If you're not getting the inline reply form -- if you're getting redirected to another page to comment -- please clear your cache and then restart your browser.

PLEASE NOTE: If you're coming to report an entry in your journal not displaying properly, and there's a <table> in the entry (or you're reporting a problem with your journal displaying properly and there's an entry with a <table> somewhere visible on the page): please check the entry's source and make sure the HTML of the table is constructed properly. We've made a change to our HTML cleaner to be more strict about missing tags and tags that were closed in a different order than they were opened. Most of the display problems people have reported have been because a table in an entry was missing closing </td>/</tr>tags!

Flat | Top-Level Comments Only

Oooh, thank you for refining the tag arrows! I love this feature (so handy for when I'm browsing fic comms) but this definitely makes the tags easier on the eye. LOVE YOU GUYS. ♥

I'm super-excited about this as well! One question: I noticed that I have to re-select the tag each time I go forward or backward while browsing via the tags. Are there plans to make it so that whichever tag you are browsing is auto-selected (with a possible option to switch tags) to better facilitate skimming through those entries?

Should work that way now!

It seems to be working, but now the arrows are floating in my page text? It's doing this on every page, and placement of the arrows seems to be related to the appearance of the bottom of the page before scrolling.

Screenshot of the arrows at the bottom of the page: http://postimg.org/image/5ras4idrt/

And of the floating arrows after scrolling down: http://postimg.org/image/6isjlyfyl/

Thanks for the report! We will definitely look into this.

Seconding this.

(And thank you, thank you, thank you, developers, for switching to the little button for the arrow option! Glitches such as the above aside, this is an excellent combination of making the feature available for those who want it and making it go away for those who don't.)