First, as others have mentioned, posting to drafts seems to actually post the article publicly. Is that just how it shows for the individual user, causing it to appear in “new” only for them but not for anyone else, or is that a bug with LW?
Second, I set some text as bold in a posting, it displayed as bold in the article editor… But in the actual posting… it didn’t.
Third: Google Chrome (the browser I’m currently using) has a built in spellcheck that seems to work in text entry boxes, including those for entering comments on LW. But in the article editor, it seems to not operate. I’m not sure if the problem is with Chrome or LW, but I thought I’d mention this issue at least.
New shows all categories you can see including your drafts, others can’t see your drafts. See the FAQ
This is an issue specific to browsers that use WebKit, namely safari and chrome. Unfortunately we can’t do anything about this, though it appears to be fixed in the latest WebKit (used by safari 4 beta)
I made a change such that where possible the browser spell check will be on. Firefox and safari appear to work and provide support. IE6,7,8, chrome and opera don’t.
Three issues:
First, as others have mentioned, posting to drafts seems to actually post the article publicly. Is that just how it shows for the individual user, causing it to appear in “new” only for them but not for anyone else, or is that a bug with LW?
Second, I set some text as bold in a posting, it displayed as bold in the article editor… But in the actual posting… it didn’t.
Third: Google Chrome (the browser I’m currently using) has a built in spellcheck that seems to work in text entry boxes, including those for entering comments on LW. But in the article editor, it seems to not operate. I’m not sure if the problem is with Chrome or LW, but I thought I’d mention this issue at least.
New shows all categories you can see including your drafts, others can’t see your drafts. See the FAQ
This is an issue specific to browsers that use WebKit, namely safari and chrome. Unfortunately we can’t do anything about this, though it appears to be fixed in the latest WebKit (used by safari 4 beta)
I made a change such that where possible the browser spell check will be on. Firefox and safari appear to work and provide support. IE6,7,8, chrome and opera don’t.