update page and s2 layouts
Yesterday's S2-layout-related changes weren't released yesterday; they'll be going out in today's round. We've also made a few changes to the Update Journal page, based on feedback and bug reports we've gotten. As always, this release is in progress, so changes won't take effect for another hour or so.
Changes to the Post to Journal page:
Words of Caution -- Read Before Commenting!
Known Issues
Reporting Bugs
Please read the list of notes above before commenting to see if your problem is addressed already. If it's not in the list above, you're welcome to comment to this post to report any bugs with this page. I'm reading every comment and I'll forward a list of bugs on to our engineers. Please make sure to list your browser, operating system, and screen resolution (if applicable), as that'll help us out when trying to reproduce and investigate bugs. (Just FYI, I won't be around for a few hours after I post this -- I'll be getting comment notifications, and others will keep an eye out for major problems, but if I don't reply immediately, that's why. *g*)
To help us to make sure that each bug report is addressed appropriately, please avoid commenting here just to express your opinion about this page -- we know there are people who dislike it (and that there are people who like it, too). If you'd like to provide your feedback about the design of the page, I encourage you to comment over in
lj_design, instead. Thanks!
Changes to the Post to Journal page:
- Fixed the sidescroll behavior when your window was narrower than a certain width (it now fits into 800x600)
- Fixed the problem where the Subject entry box would be really small in Safari
- Fixed the problem where editing entries didn't allow you to change the date/time on them
- Added a maximum width to the page, too, so the page doesn't get too wide on larger resolutions.
- Increased the font size in the entry box in the HTML editor
- Changed the font in the HTML editor from Arial to Verdana (with a fallback to Courier)
- Fixed the bug that caused the loss of formatting when switching between HTML and Rich Text
- Some stylistic changes to the page to make it be less white
- Fixed the bug that caused "Bad Unicode Input" errors when you tried to post using a custom filter.
Words of Caution -- Read Before Commenting!
- If you aren't seeing any of these changes, or if the page is acting weird: please force-refresh the page and/or clear your browser's cache, to make sure you're getting the most up-to-date versions of the stylesheets and JavaScript files. (Many problems magically go away that way. *g*)
- If you're having problems posting, make sure you're using the right entry editor. In particular, you might be using the Rich Text editor (which doesn't allow HTML formatting) instead of the HTML editor, so check the tab on the top right corner to see which you're using.
- If you don't see the Rich Text/HTML tabs at all, it's likely because you're using Safari or Opera (or have JavaScript disabled). Those browsers don't support the Rich Text editor, so the option to use the Rich Text editor doesn't display. You'll default back to using the HTML editor, as normal.
- If you're having problems switching back and forth from Rich Text to HTML, it's likely because your browser is outdated -- older versions of Firefox/Mozilla have a bit of trouble switching back to HTML from Rich Text. Try upgrading your browser and try again. You can also specifically choose to only use the HTML (plain text) editor.
- If you're looking for the "Backdate" option: it's been renamed to "Date out of order", and you can access it by clicking the "Edit" link next to the date/time. If you're trying to figure out where the post-to-community dropdown is: it's at the top of the page.
Known Issues
- Using the "insert image" button in the HTML editor and trying to add an image from your ScrapBook won't work. We'll fix, but in the meantime, you'll need to post your images directly from ScrapBook.
- Custom filter options aren't displaying in Internet Explorer (apparently as a side effect of us fixing one of the bugs above...). In the meantime, try a different browser to post. We'll fix the root problem ASAP, though.
Reporting Bugs
Please read the list of notes above before commenting to see if your problem is addressed already. If it's not in the list above, you're welcome to comment to this post to report any bugs with this page. I'm reading every comment and I'll forward a list of bugs on to our engineers. Please make sure to list your browser, operating system, and screen resolution (if applicable), as that'll help us out when trying to reproduce and investigate bugs. (Just FYI, I won't be around for a few hours after I post this -- I'll be getting comment notifications, and others will keep an eye out for major problems, but if I don't reply immediately, that's why. *g*)
To help us to make sure that each bug report is addressed appropriately, please avoid commenting here just to express your opinion about this page -- we know there are people who dislike it (and that there are people who like it, too). If you'd like to provide your feedback about the design of the page, I encourage you to comment over in
lj_design, instead. Thanks!