Denise (
denise) wrote in
dw_maintenance2015-03-16 12:27 am
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
(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!
(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!
no subject
I would rather be unconscious, honestly, it would be better than being 70% fine and 30% cognitively impaired and not necessarily being able to tell which part is the 30%. :P I'm just really freaking slow right now. Doesn't help I was supposed to go to sleep a few hours back but the pain's keeping me awake.
Anyway, yeah, people are going to have to be a lot more vigilant about making sure that a) all the tags you open get a corresponding closing tag b) that are closed in the (reverse) order they were opened. Like, if you have a <center<table><tr><td>, you need to close them in the exact order of </td></tr></table></center>. Previously we were more lenient about that and the HTML cleaner would try to detect mismatched tags and close them as necessary, but a few display bugs and pagebreaking tricks were exploiting that, so we had to tighten up the leeway. I know people got used to the cleaner being very permissive about what it would accept without breaking the view, so it'll be a bit of an adjustment, but the change was necessary.
no subject
Try and get some unconscious time as soon as you're able ♥