dw_beta: New JS on Journals: Last Call

fu (

fu) wrote in

dw_beta,
@ 2012-03-24 01:20 pm UTC

New JS on Journals: Last Call

We're planning on taking the "new JavaScript on journals" changes out of beta soon and making the changes the default for the entire site, so we've done a push today that adds the last few (reported) missing features, and fixes the last few (reported) really annoying behaviors.

There's always going to be one thing more though, so please make sure that you turn on beta for the new JS on journals, and tell us how that new JS works for you -- or doesn't work, if that's the case.

I'm interested in hearing about everything that's bothering you, no matter how tiny it seems! The sooner we know, the sooner we can fix it. (Just this code push, we fixed two things that seemed tiny: one was the hover menu fading way too quickly, another was how the attempt to change your poll vote would bring to you to a separate page instead of changing your vote on the page you were on. They were both things we missed at first, but once they were brought to our attention, we couldn't stop seeing them. And now they're fixed!)

So poke around, and let us know what you find. If you're looking for something to focus on, here's a short list of things we recently added or fixed:

added same-page comment tracking

fixed same-page changing of poll votes

added displaying errors when comment expansion fails to work

fixed hover menu fading away even when you didn't move your mouse

fixed the .cuttag-open CSS class so it applies to the contents of the opened cut tag (the way the old JS did), for people who want to customize this in their styles

made the bottom arrow jump you to the top of the cut tag, without affecting page forward/back

Assuming there are no major issues, we'll turn on the "new JS on journals" beta flag for everyone with our next code push for one last round of testing with the whole site, not just the people who've turned on the beta version. We'll keep it as a beta option at that point, so if anyone has serious problems, they can disable the beta and go back to the old JS while we fix the problem. After that, we'll take this code out of beta and make it the standard option for everyone, removing the old (existing) JavaScript entirely. So, if something's wrong, speak up now!

Page 1 of 2

<< [1] [2] >>

(123 comments) - (Post a new comment)
(Flat) (Top-level comments only) (Expand All)

no subject

northern
2012-03-24 05:59 am UTC (link)

The hover menu for icons (you have subscribed to fu!) on my friends page doesn't go away at all, even though I move my mouse away. It doesn't go away until I actually click somewhere else. Is that a feature or a bug? (The same thing seems to work differently for example for the commenting page, which I am on now to write this comment - the menu stays about a second or so after I've removed the mouse from the icon, but then goes away.)

(Reply to this) (Thread) (Expand) (Hide 7 comments) (Show 7 comments)

	no subject kareila 2012-03-24 06:18 am UTC (link)
	The delayed fadeout is a new feature - I think it was staying on indefinitely before, at least in the beta. For me the hover menu on the reading page works as expected the first time, but then it flashes off immediately if I bring the same one up again. (Using Google Chrome.) Definitely some inconsistency there. (Reply to this) (Thread from start) (Parent)

(no subject) -

northern, 2012-03-24 06:20 am UTC (Expand)

(no subject) -

widowmaker, 2012-03-24 06:40 am UTC (Expand)

(no subject) -

pocketmouse, 2012-03-24 04:45 pm UTC (Expand)

(no subject) -

darksilverhawk, 2012-03-26 05:24 pm UTC (Expand)

(no subject) -

thomasneo, 2012-07-04 08:52 am UTC (Expand)

(no subject) -

ninetydegrees, 2012-08-20 07:27 pm UTC (Expand)

	no subject unicorn 2012-03-24 06:59 am UTC (link)
	The extra rows combined with the fullsize icons in the new icon selector gives me visual fatigue; I went into it a little more here. I would love it if we could at least have size options on the selector like we did in the previous one. (Reply to this) (Thread) (Expand) (Hide 9 comments) (Show 9 comments)

	no subject memorable 2012-03-24 07:02 am UTC (link)
	I'm also having problems with this! The number of icons in a row plus the size of the icons is way too much for me to handle. (Reply to this) (Thread from start) (Parent)

(no subject) -

all_that_glitters, 2012-03-24 07:11 am UTC (Expand)

(no subject) -

antreegonist, 2012-03-24 07:16 am UTC (Expand)

now commenting in the right place! -

unwieldyfate, 2012-03-24 07:27 am UTC (Expand)

(no subject) -

basilmemories, 2012-03-24 07:40 am UTC (Expand)

(no subject) -

basilmemories, 2012-03-24 07:44 am UTC (Expand)

(no subject) -

nevergetscredit, 2012-03-24 08:38 am UTC (Expand)

(no subject) -

ketsu, 2012-03-25 01:49 am UTC (Expand)

(no subject) -

momijizukamori, 2012-03-25 02:12 am UTC (Expand)

no subject

articletwelve
2012-03-24 09:06 am UTC (link)

Slightly contrary to those above, but I love this icon browser's width and size and just being able to sort through so many icons without as much scrolling. The one nagging thing is that the browser doesn't remember it when I click "Images only" or "Show meta text" past that particular instance. Is this something that can be set or cookied in some way, or is it stuck as something to pick every time? I'd happily just use images only all the time, but since there's no way to stick with it I never bother with the setting.

Also, not sure if I should mention stuff about the Create Entries beta here, but there's one thing on that that drives me nuts -- the title attribute on the main entry textarea. Whenever I'm writing something that involves a lot of coding, or just selecting text in general, or if I simply leave my cursor there, the bubble pops up and gets to be very annoying. I know that it's important for accessibility to label the textarea, but it would be a lot less frustrating if it were using the alt attribute instead so that it didn't constantly pop up.

(Reply to this) (Thread) (Hide 6 comments) (Show 6 comments)

	no subject denise 2012-03-24 09:11 am UTC (link)
	Hm, it remembers the setting (icon only / meta text) for me. What browser and OS are you using? (Reply to this) (Thread from start) (Parent) (Thread) (Expand) (Hide 5 comments) (Show 5 comments)

(no subject) -

articletwelve, 2012-03-24 09:13 am UTC (Expand)

(no subject) -

denise, 2012-03-24 09:21 am UTC (Expand)

(no subject) -

articletwelve, 2012-03-24 03:26 pm UTC (Expand)

(no subject) -

denise, 2012-03-25 05:32 pm UTC (Expand)

(no subject) -

articletwelve, 2012-03-25 09:41 pm UTC (Expand)

no subject

lethe1
2012-03-24 07:04 pm UTC (link)

I'm having problems with the new icon browser in both of my (admittedly very old) browsers.

In Safari (1.3.2), if I click on Browse nothing happens at all. In Firefox (1.0), a window pops up that is so small that I can only see part of one icon, and I need to scroll down to see the rest of it and the keyword, never mind the rest of my icons.

The previous icon browser worked perfectly in both Safari and Firefox, including the options for changing the icon sizes, which is a feature I'd really like to keep.

(Reply to this) (Thread) (Hide 6 comments) (Show 6 comments)

	no subject denise 2012-03-25 05:33 pm UTC (link)
	Just to doublecheck, do you have Javascript enabled (and if you use an extension like NoScript that selectively enables JS, do you have dreamwidth.org -- not www.dreamwidth.org -- whitelisted?) (Reply to this) (Thread from start) (Parent) (Thread) (Expand) (Hide 5 comments) (Show 5 comments)

(no subject) -

lethe1, 2012-03-25 05:44 pm UTC (Expand)

(no subject) -

denise, 2012-03-25 06:04 pm UTC (Expand)

(no subject) -

lethe1, 2012-03-25 07:02 pm UTC (Expand)

(no subject) -

denise, 2012-03-25 07:06 pm UTC (Expand)

(no subject) -

lethe1, 2012-03-25 07:21 pm UTC (Expand)

	no subject thenormalsquint 2012-03-25 07:53 am UTC (link)
	Directed here by Denise. I cleared my cache and cookies, rebooted both my computer and my browser and the problem with Expand All hanging and freezing remains. I'm on Firefox 7.0.1 with Adblock, Adblock Element Hider, and Ghostery (which I tried whitelisting DW on thinking it would help, but nope.) (Reply to this) (Thread) (Expand) (Hide 12 comments) (Show 12 comments)

no subject

denise
2012-03-25 05:23 pm UTC (link)

eyesofstrength, below, was having a similar problem and narrowed it down to three extensions (tab counter, tab mix plus and tabs menu) -- do you have any of those installed? If not, can you try the exclusion method I described in this comment and see if you can narrow down which extensions are causing the problem?

(Reply to this) (Thread from start) (Parent) (Thread) (Expand) (Hide 7 comments) (Show 7 comments)

(no subject) -

pocketmouse, 2012-03-25 06:02 pm UTC (Expand)

(no subject) -

denise, 2012-03-25 06:58 pm UTC (Expand)

(no subject) -

pocketmouse, 2012-03-25 07:06 pm UTC (Expand)

(no subject) -

fu, 2012-03-27 08:56 am UTC (Expand)

(no subject) -

pocketmouse, 2012-03-27 11:56 am UTC (Expand)

(no subject) -

funkybrewsta, 2012-03-26 04:48 am UTC (Expand)

(no subject) -

fu, 2012-03-27 08:49 am UTC (Expand)

(no subject) -

fu, 2012-03-27 08:55 am UTC (Expand)

(no subject) -

thenormalsquint, 2012-03-27 08:58 am UTC (Expand)

(no subject) -

thenormalsquint, 2012-03-27 09:13 am UTC (Expand)

(no subject) -

fu, 2012-03-27 09:16 am UTC (Expand)

no subject

eyesofstrength
2012-03-25 03:07 pm UTC (link)

I've actually been having issues expanding comments for some time, but I've been opted into the beta for months, just had no idea it was beta related. I have two computers and it only happens on one of them. The other works perfectly fine and is nearly the same setup except OS is different since it's newer.

Affected computer has following setup:

OS: Windows XP (fully updated)
Browser: Firefox 3.6.4
Add-ons: Adblock plus, greasemonkey, ljlogin, noscript (and DW is fully allowed), session manager, tab counter, tab mix plus, tabs menu and youtube to mp3

The computer that works uses same version and has all those add-ons but a few additional ones like Stylish. Only other difference is it uses Windows 7 instead of XP. I can provide a more detailed list of add-ons for the working one later once I'm off work.

And on this computer, expanding works fine in Chrome, but I hate using Chrome on this computer because it will give me a BSOD once a day.

(Reply to this) (Thread) (Expand) (Hide 13 comments) (Show 13 comments)

no subject

denise
2012-03-25 03:16 pm UTC (link)

Just to gather some data/run some quick exclusion tests:

* If you disable the extensions on the computer you're having problems with, does the problem go away?

* If you only disable LJLogin, does the problem go away? (We have had many, many reports of LJLogin causing all kinds of grief in various ways -- if you're looking for something that will easily let you log in/log out as various accounts, I strongly strongly recommend CookieSwap or a similar full-cookie-profile-swapping extension, instead of LJLogin, until we can do the main/alternate account system we've been planning for a while!)

* Just to clarify (since your comment could've been taken one of two ways) -- is the affected computer the one that Chrome works on, or is that a different computer? In other words: do you have the same problem expanding threads in other browsers on the computer that's having the problem expanding threads in Firefox?

(Reply to this) (Thread from start) (Parent) (Thread) (Expand) (Hide 10 comments) (Show 10 comments)

(no subject) -

eyesofstrength, 2012-03-25 04:19 pm UTC (Expand)

(no subject) -

denise, 2012-03-25 04:21 pm UTC (Expand)

(no subject) -

eyesofstrength, 2012-03-25 04:25 pm UTC (Expand)

(no subject) -

denise, 2012-03-25 04:37 pm UTC (Expand)

(no subject) -

eyesofstrength, 2012-03-25 05:11 pm UTC (Expand)

(no subject) -

denise, 2012-03-25 05:21 pm UTC (Expand)

(no subject) -

eyesofstrength, 2012-03-25 05:52 pm UTC (Expand)

(no subject) -

eyesofstrength, 2012-03-25 10:44 pm UTC (Expand)

(no subject) -

fu, 2012-03-27 08:45 am UTC (Expand)

(no subject) -

eyesofstrength, 2012-03-27 02:22 pm UTC (Expand)

(no subject) -

fu, 2012-03-27 08:53 am UTC (Expand)

(no subject) -

eyesofstrength, 2012-03-27 03:14 pm UTC (Expand)

no subject

pocketmouse
2012-03-25 05:17 pm UTC (link)

OK, I just answered a bunch of polls at dw_suggestions, and every time I voted from my reading page, after voting I'd end up on the entry page on suggestions. I wasn't changing my vote, this was my initial vote.

Previous to today, I last voted probably on the 18th-19th, with the last set of suggestions. I don't recall if I voted anywhere else, so I think this issue came in with the code push.

(Reply to this) (Thread) (Expand) (Hide 9 comments) (Show 9 comments)

	no subject runpunkrun 2012-03-26 12:08 am UTC (link)
	Yeah, this happened to me today as well. Answering a poll took me to the poll page, then, back on my reading list, the "view answers" link also took me to the poll page. Basically interacting with polls takes me somewhere else instead of letting me do that from my reading list, like it used to. (Reply to this) (Thread from start) (Parent) (Thread) (Expand) (Hide 2 comments) (Show 2 comments)

(no subject) -

fu, 2012-03-27 08:39 am UTC (Expand)

(no subject) -

runpunkrun, 2012-03-27 05:19 pm UTC (Expand)

(no subject) -

fu, 2012-03-27 08:38 am UTC (Expand)

(no subject) -

pocketmouse, 2012-03-27 11:53 am UTC (Expand)

(no subject) -

sarken, 2012-03-31 06:26 am UTC (Expand)

(no subject) -

fu, 2012-03-31 07:32 am UTC (Expand)

(no subject) -

sarken, 2012-03-31 07:53 am UTC (Expand)

(no subject) -

fu, 2012-03-31 08:48 am UTC (Expand)

no subject

xnera
2012-03-26 12:48 am UTC (link)

Browsing a few longer threads on

cfud tonight, and getting Unresponsive Script Errors when I try to expand them. One of the threads that threw the error was this one: http://cfud.dreamwidth.org/6388099.html?thread=3096672899#cmt3096672899

I turned off beta-testing, refreshed the page, and clicked the Expand link again, and it loaded just fine then, if a bit slow. But, I'd rather have slow loading than error messages!

Using Camino Version 2.1.2 (1.9.2.28 20120308211433). Camino is a port of Firefox for Macs, in case you aren't familiar with it.

Out of curiosity, I tried it in Safari on another account of mine, and had no problems, both with/without betatesting turned on. So it looks like it's definitely a Camino issue.

(Reply to this) (Thread) (Hide 1 comment) (Show 1 comment)

	no subject fu 2012-03-27 08:50 am UTC (link)
	Hmm, it looks like our approach is reasonably fast on Chrome and Safari (and from testing, Opera), but pretty slow on Firefox-based engines. Thanks for that info! (Reply to this) (Thread from start) (Parent)

no subject

chagrined
2012-03-26 10:56 pm UTC (link)

Sorry this is so late, but I only noticed this now b/c a friend pointed it out to me (since I had this feature turned off). They discovered that when they tried to leave the first comment on an entry of mine with zero prior comments, using the inline-commenting tool (rather than loading the whole page with ?mode=reply), for some reason the comment box appears on the far side of my journal like so: http://i.imgur.com/JVP7j.png

This only happens on the first comment; after that everything is fine. I tested this as well after turning the beta feature on and got the same result. I suspect this might be in part b/c I am using a style that is ported from LJ, and maybe it's got something different in how it's written from the DW styles, and possibly this is not something DW is concerned with if that's why it's happening. But in case it happens with DW styles too or just so you know anyway, thought I'd mention it. :)

(Reply to this) (Thread) (Hide 1 comment) (Show 1 comment)

	no subject denise 2012-03-26 11:45 pm UTC (link)
	Hm. Do you have the same problem with a DW-native style? (If not, I don't know whether we'll be able to fix it or not; you may need to fix it in the style itself.) (Reply to this) (Thread from start) (Parent)

	no subject brisus 2012-03-28 12:03 am UTC (link)
	I'm sure this is a WIP, but choices to crosspost? (Reply to this) (Thread) (Hide 2 comments) (Show 2 comments)

	no subject denise 2012-03-28 07:32 am UTC (link)
	You've probably turned on the second beta test, the new create entries page. Hit the gear icon in the upper right, and then you can check or uncheck whatever boxes you'd like (including crossposting) (Reply to this) (Thread from start) (Parent) (Thread) (Expand) (Hide 1 comment) (Show 1 comment)

(no subject) -

brisus, 2012-03-28 12:29 pm UTC (Expand)

	no subject bjornwilde 2012-03-28 09:46 pm UTC (link)
	I'm likely being lame but how do I get the rich text tab back for when I make/write a post? Apologizes if this has already been covered. (Reply to this) (Thread) (Hide 1 comment) (Show 1 comment)

	no subject denise 2012-03-28 11:45 pm UTC (link)
	Rich text isn't implemented in the Create Entries beta yet. If you need the rich text editor, go back to http://www.dreamwidth.org/betafeatures and turn off the second of the two beta tests. (Reply to this) (Thread from start) (Parent)

no subject

blue_wayfinder
2012-03-29 02:02 am UTC (link)

I was told that the following script failed to run earlier when I tried to expand a thread:

http://www.dreamwidth.org/js/??jquery/jquery-1.5.2.min.js,dw/dw-core.js,jquery/jquery.ui.widget.min.js,jquery.ajaxtip.js,tooltip.min.js,jquery/jquery.ui.position.min.js,jquery.hoverIntent.js,jquery.contextualhover.js,nav-jquery.js,jquery.threadexpander.js,jquery.poll.js,jquery.mediaplaceholder.js,jquery.quickreply.js,jquery/jquery.ui.core.min.js,jquery/jquery.ui.dialog.min.js,jquery.iconselector.js,jquery.commentmanage.js,md5.js,login-jquery.js?v=1332564315:16

But the thread in question expanded fine though for a moment after clicking it my browser looked like it was ready to crash until it asked me if I wanted to stop the script.

I'm currently using Firefox if that helps any.

(Reply to this)

	no subject storyfan 2012-03-30 05:21 am UTC (link)
	I must be an idiot because I can't see where to embed media. (Reply to this) (Thread) (Hide 2 comments) (Show 2 comments)

	no subject denise 2012-03-30 07:05 am UTC (link)
	Rich text is not yet enabled in the Create Entries beta. That's a separate beta test from the new Javascript. If you need rich text, you can go back to http://ww.dreamwidth.org/betafeatures and turn off the second of the two options (the Create Entries beta)! (Reply to this) (Thread from start) (Parent) (Thread) (Expand) (Hide 1 comment) (Show 1 comment)

Ia! Ia! 404 Fhtagn! -

onyxlynx, 2012-04-07 06:09 pm UTC (Expand)

no subject

onyxlynx
2012-04-07 06:07 pm UTC (link)

Don't know if anyone's brought it up yet: I created an entry in beta which I set aside to post something else and when I went back to post the first item I ~~fell into a time warp~~ got a message that I needed to check "Don't show on reading page," which of course one can't do in beta; there's no way one can "post-date" in beta. This is probably one of the items that will be added back later. I simply hadn't noticed it wasn't there.

(Reply to this)

no subject

minifridge
2012-04-11 08:50 pm UTC (link)

I'm another one having trouble expanding comments on my two accounts that are using beta features. It's extremely laggy - as in it kind of never works ever - and refreshing the page doesn't help, no matter what. If I switch to an account without beta features, then expanding works fine. No error messages, it just says "loading" forever.

For clarification:

- I'm using up-to-date Firefox on a Mac, ljlogin, Adblock Plus, and Greasemonkey (but my only script is for LJ and I don't think I have it turned on anyway), and I never had this problem before turning on beta features yesterday.

- I've actually only been on site skin pages so far, so I can't tell you if it happens on custom comment pages.

Hope this helps!

(Reply to this) (Thread) (Hide 4 comments) (Show 4 comments)

	no subject denise 2012-04-11 08:55 pm UTC (link)
	Does it happen on every account, or just on accounts with deeply nested threads? (Reply to this) (Thread from start) (Parent) (Thread) (Expand) (Hide 3 comments) (Show 3 comments)

(no subject) -

minifridge, 2012-04-11 09:03 pm UTC (Expand)

(no subject) -

denise, 2012-04-11 09:08 pm UTC (Expand)

(no subject) -

minifridge, 2012-04-11 09:12 pm UTC (Expand)

	no subject turlough 2012-04-16 07:58 pm UTC (link)
	I know I'm late with this but I'm wondering, is there any way to navigate the new icon browser using keyboard commands? I can't seem to find any key combinations that work. If there isn't there really should be. I didn't realise how much I missed it until LJ changed so you could navigate their new browser with the arrow keys. (Reply to this)

	no subject sophie 2012-04-16 09:47 pm UTC (link)
	This (probably) isn't a bug, but I don't really like the amount of space that's now given in- between collapsed comments in the new JS beta; I liked it better closer together. Maybe it's an accessibility thing, though? (Reply to this)

no subject

cesy
2012-04-19 07:22 pm UTC (link)

I'm hitting an odd issue with tracking comments - I can click on "Track This", get the AJAX popup thingy, choose to track comments on that entry, click save, and it apparently does save if I check in another tab or refresh the window, but it still says "Track This" instead of "Untrack This", so it looks like that part isn't refreshing properly. I think it used to, otherwise it wouldn't be confusing me this much?

I'm using the current Chrome on Windows 7 and have Adblock, Stylish and a few other extensions, but none that I'd guess are interfering here.

Last edited 2012-04-19 07:23 pm UTC (forgot to say what browser I'm using)

(Reply to this)

no subject

baggyeyes
2012-04-29 11:15 pm UTC (link)

I have no doubt that I'm late - but I ran into a weird problem using Opera 11.62 (Mac) trying to post a new entry.

The page loaded fine, no problem; I wrote my entry and added the currents, then tried to click Post Entry. Nothing happened. This didn't happen before in Opera, so I'm a bit confuzzled. Or something.

This is the error I received:

 
HTML style attribute
Unknown pseudo class
Line 1:
.ajaxtip:visible

And a new Post error, this time in Opera Next, ver. 12.00 beta, build 1387 (Mac OS)


Error
Client error: Invalid argument(s): Invalid year value (must be in the range 1970-2037).

Last edited 2012-05-01 12:40 am UTC

(Reply to this)

no subject

earnedmystripes
2012-05-17 12:36 am UTC (link)

hello! I very recently discovered issues relating to the 'post new comment' button and the javascript on beta that handles thread and cut expansion, as well as the 'browse' and 'random entries' buttons on the create entries page.

I've made a support request here with the details of the problem and what I've attempted to do to resolve the problems on my own, and a friend suggested I comment here as well.

Thank you for your time!

Last edited 2012-05-17 12:37 am UTC

(Reply to this)

no subject

eyesofstrength
2012-07-02 07:50 pm UTC (link)

And since news advised it and I happened to have my secondary computer on, still having the same thread expansion issue on one computer only that only turning the beta off seems to resolve. Basically the one where it sits there loading forever and doesn't expand the thread.

And honestly, using the beta bogs down thread expansion a lot even on the computer it does work on, often temporarily freezing my browser with a long thread for a minute or more and that is not in the least bit tolerable when the current one works almost instantly.

(Reply to this)

	no subject seleneheart 2012-08-10 08:53 pm UTC (link)
	The new post entries page doesn't auto-save. Using Firefox, latest version. (Reply to this) (Thread) (Hide 1 comment) (Show 1 comment)

	no subject denise 2012-08-10 08:59 pm UTC (link)
	Yup, that's one part of it that hasn't been implemented yet (fu is working on it). That's not part of this particular beta-feature test, though -- this is just for the new JavaScript inside the journal itself, not the new update page! (Which is definitely further away from being ready to take out of beta.) (Reply to this) (Thread from start) (Parent)

	no subject pascendi 2012-08-17 07:03 pm UTC (link)
	The new posting form does not have any information (to say nothing for the possibility to change it) about the time of the post. Please correct it, it's a necessary feature. (Reply to this) (Thread) (Hide 1 comment) (Show 1 comment)

	no subject denise 2012-08-17 07:06 pm UTC (link)
	Hit the gear icon in the upper right corner and enable the "Display Date" module. Date and time can then be changed by hitting the icon next to the timestamp in that module. (Reply to this) (Thread from start) (Parent)

	no subject theplotbunny 2012-08-20 06:18 pm UTC (link)
	I noticed that as I toggled to each field with my screen reader, the page kept reading that I was testing the new beta or something, and I couldn't use the field for this as it operates like a pop-up, it confused and frustrated me as it seemed to be tracking myy vertual cursor (Reply to this)

no subject

ketsudan
2012-09-20 06:11 am UTC (link)

This is kind of late in the game, but I enabled the beta for posting entries, and I am adoring this. I love how I can select what I want to show when and where, and that I can change this at any time.

The interface isn't the prettiest, but it's clean and minimalistic, which is a breath of fresh air, as other sites do not have this, or are changing from it. Why they would do this, I don't know.

The interface that you have for browsing tags is lovely too, but maybe you could somehow work it so longer tags are still on one line?

I am not sure how LiveJournal does it, but their tag browsing interface has that. If I recall correctly, the longer ones kind of fade before they get to the next column (so you don't see the whole thing), instead of wrapping to the next line like yours does. I think that LJ's version might not be good for longer tags that need to be read completely.

Maybe you could do a smaller font? I have terrible eyesight, and I am sure that something a bit smaller wouldn't hinder me, maybe something along the 9-10px range.

One more added critique for the tag browser, is that instead of having the list go from left to right like this:

A B C D
E F G H

It could go like a typical list:

A E
B F
C G
D H

I just think that might be a little easier, as the eyes naturally go down and then up and over when reading lists, while with full paragraphs with text, they go from left to right and then down to the left again.

But all in all, this is a wonderful posting page and I love it!

EDIT:

Also, still on the topic of the tag selector, could it be possible to have the "save" button down at the bottom of that screen? It's kind of awkward for it to be up in the top right when all other save or update buttons are down at the bottom left or bottom right.

But this is just minor and me nitpicking, I am sure that there are lots more important suggestions.

Last edited 2012-09-21 04:18 pm UTC

(Reply to this)

(123 comments) - (Post a new comment)
(Flat) (Top-level comments only) (Expand All)

Page 1 of 2

<< [1] [2] >>

Account name:	Log in with OpenID?
Password:	Forget your password?
	Remember me