Live data from Hacker News

Lousy web design trends that are making a comeback due to HTML5

econsultancy.com

121–130 of 145 posts

Re: Lousy web design trends that are making a comeback due to HTML5

#121

I especially agree with regard to loading screens. For example some blogs have this "gears" animation before they display their text. I'm not sure who ever came up with thinking that might be a good idea... even if the site is slow that it required a few seconds of loading, just showing text and images incrementally means that you can start reading immediately instead of waiting for the "funny" animation.

Not "some" but first and foremost Blogger from Google. Awful.

Re: Lousy web design trends that are making a comeback due to HTML5

#122

Earlier quoted context omitted.

>there are dummy social buttons loaded by default, you have to "enable" them Neat. This looks like a very reasonable way to go if you decide to have social buttons. Is there a ready-made solution for this?

> Is there a ready-made solution for this? https://github.com/filamentgroup/SocialCount I'd be interested in learning about good alternatives.

Another is https://github.com/mischat/shareNice. They look like they do pretty much the same thing: Serve the icons themselves, and just make them a link to the respective services.

For example:

- https://www.facebook.com/sharer/sharer.php?u=[Url to share]

SocialCount looks like it also cares about how many times a link has been shared, and uses a server-side script to figure that out. That seems like a nice approach if you really want that info, because it doesn't let the social service track the end user.

shareNice seems to have a wider range of services that it supports.

Re: Lousy web design trends that are making a comeback due to HTML5

#123

Earlier quoted context omitted.

Unless they use any other tracking system, like ETags[1]. [1]: http://en.wikipedia.org/wiki/HTTP_ETag#Tracking_using_ETags

Disable fetching any third party resources of all sorts, problem solved. Obviously, rulesets should be tuples of (source pattern, resource type, destination pattern), not silly lists ("allow google.com", huh?) like most browser extensions do.

I am using Ghostery, which does a pretty good job of intelligently blocking (and also notifying me) of trackers.

However, there are some sites that stupidly execute JS that is vital to the running of the page after attempting to initialize Google Analytics or other services. The end result is that they get a "Cannot call method 'bleh' of undefined" error which prevents the rest of their JS executing, hence broken page. If I'm really interested in actually loading the page, then I have to resort to allowing the trackers to run. sigh.

Unfortunately, I can't see how this could be averted, stopping short of an extension which catches all uncaught exceptions, then tries to forcefully remove all JS which is meant to interact with 3rd parties. It could be done either via pattern matching, because Google Analytics code looks much the same on most peoples sites, or it could be through something more fun, like https://github.com/mattdiamond/fuckitjs (who would of thought there would actually be a proper use case for something like that??)

Re: Lousy web design trends that are making a comeback due to HTML5

#124
post #34

Under the "Contrast Fail" is my single largest pet-peeve of form design. Once you click over that form, the text goes away and you may not know where you are. Please use labels, people. I have no idea why he didn't include that in this article.

This. Unless your form is incredibly simple (e.g. signup or login) you shouldn't just rely on placeholder text. Apple has a nice solution to this issue on their checkout pages - labels placed on top of inputs, only disappearing once text is entered.

>This.

Hi, samefag.

Re: Lousy web design trends that are making a comeback due to HTML5

#126

Earlier quoted context omitted.

Disable fetching any third party resources of all sorts, problem solved. Obviously, rulesets should be tuples of (source pattern, resource type, destination pattern), not silly lists ("allow google.com", huh?) like most browser extensions do.

I am using Ghostery, which does a pretty good job of intelligently blocking (and also notifying me) of trackers. However, there are some sites that stupidly execute JS that is vital to the running of the page after attempting to initialize Google Analytics or other services. The end result is that they get a "Cannot call method 'bleh' of undefined" error which prevents the rest of their JS executing, hence broken pag…

For some of the bigger ones the extension could try to keep some dummy scripts that match the api properly. e.g. make it look like GA started but not actually send them anything at all. Though that sounds like a cat and mouse game.

Re: Lousy web design trends that are making a comeback due to HTML5

#128
post #55

The trend that annoys me most right now is that image thumbnails never just point to the large image: instead they pop up some JS-based overlay that obscures the whole page. There are several issues with this: * Quite often, for whatever reason, the overlay takes seconds to load (much longer than just loading the image) * If the image takes long time to load, I cannot just put it in a background tab and continue brow…

At a bare minimum, people using lightboxes for images should have the link actually point to the image, and have the click handler both open the lightbox and suppress the default click behavior. That way, opening the image in a new tab (with a middle-click or right-click+context-menu) still works as expected for users that want to do that.

Re: Lousy web design trends that are making a comeback due to HTML5

#129

Earlier quoted context omitted.

Unless they use any other tracking system, like ETags[1]. [1]: http://en.wikipedia.org/wiki/HTTP_ETag#Tracking_using_ETags

Disable fetching any third party resources of all sorts, problem solved. Obviously, rulesets should be tuples of (source pattern, resource type, destination pattern), not silly lists ("allow google.com", huh?) like most browser extensions do.

that could break a lot of sites that use a cdn for speed :-(

Re: Lousy web design trends that are making a comeback due to HTML5

#130
post #23

What strikes me most is how websites are visually getting more and more minimalistic and at the same time they're loading and working slower. For example The New York Times [1] layout is as simple as possible (basically text only with some images), but it loads 20 JS files, 13 CSS files, makes ~200 requests and uses ~14 MB of memory on load. [1] http://www.nytimes.com/

It's hard to believe that a site with that kind of traffic & resources hasn't even bothered to concatenate and minify its JS & CSS. Most of the JS files still have comments. Bizarre. They should know better.

its old school publishers who often have very little idea what they are doing and have sclerotic development processes 9 week sprints! in one case.

One site I worked on did not manage to sort out a redirect of its .net version of its domain and its over 2 Years since a flagged this as a high priority problem.

Post reply on HN