SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I would show both links to those that do make the rules there, since the other search engines will probably follow Google soon and start penalizing such blocked sites.
Depending on the country in which the site is based, failing to provide a working site may be in violation of accessibility laws.
Save both work and increase your market by n percent by using HTML and CSS instead of JS.
Edit: Here are two positive examples of using CSS without requiring JS:
You did solicit feedback by posting here, but hey, I'll go with #3 instead.
3. Ignore broken sites, just like the search engines do
Here's the website displayed by two different browsers on a Slackware64 14.1 system.
1. Mozilla Firefox 45.8.0 ESR (default configuration).
2. Links.
I suggest you just use the standard Firefox configuration. Or any other browser on any other system, for the matter. I did ask for feedback on the site's content indeed. If you want to discuss the pros and cons of mobile-friendly web design, I don't think this is the appropriate place to do this. Thank you.
The new one just has slowly rotating curved lines in the middle of the browser window.
Quote:
Originally Posted by TracyTiger
I'm not sure if you're being sarcastic or not. My experience on the site was the same as yours until I temporarily turned on javascript for the site, then the site worked for me.
Quote:
Originally Posted by Turbocapitalist
Save both work and increase your market by n percent by using HTML and CSS instead of JS.
Edit: Here are two positive examples of using CSS without requiring JS:
Well neither of you are exactly correct. The site displays an overlay hiding content, yes, that won't go away if js is disabled. But, if you are using NoScript, then press and hold the left mouse button on the center graphic and press delete, and then the same on the general overlay. Then you can use the site just fine without js. js is not required for this site. The overlay may be from css or standard html, I don't know this since I don't make websites.
"Customized" maybe my seamonkey (not heavily), but you gotta know how to use your browser when you see sites like this...
I generally browse on mobile devices without js btw. It speeds up sites immensely. I don't know how to kill overlays in this case (chrome on mobile). I would just get rid of that "loading" thing, and it is a fine site after that.
I also have JS disabled and the new site does not work for me.
You keep saying JS is not needed, yet the site does not work without it...
Maybe it would be better to have a fallback for such cases?
Even a simple page just saying "hey, turn on JS or this site will not work" is better that rotating lines thing.
I also have JS disabled and the new site does not work for me. You keep saying JS is not needed, yet the site does not work without it... Maybe it would be better to have a fallback for such cases?
Even a simple page just saying "hey, turn on JS or this site will not work" is better that rotating lines thing.
I agree. I can't access the site with javascript disabled in Firefox. Maybe it's specific to firefox, but many people use that and some with javascript disabled. Other than that it's beautiful, congrats
Last edited by Didier Spaier; 03-13-2017 at 05:50 PM.
To be honest if it was anyone else likely most people would not even bother to tell you that you decided to adopt current popular yet bad web design practices and moved on instead...
- Hi guys. Here's 1.558 extra packages for Slackware. And dozens of pages of documentation. Have fun
The site looks well, Niki, although I prefer the old one. You've obviously put a lot of work into it, but you should listen respectfully to criticism. I agree with TurboCapitalist that a site in 2017 should degrade gracefully. Many people disable javascript these days.
Another thing: too often I have gone looking for your guides (setting up Slackware on online.net, for example) and found them missing, or at a new address.
When I can find them, the guides are useful. The website looks good; the content is worthwhile. Don't get too upset when somebody prods you to make changes that can only be beneficial. I had a customer about 12 years ago who had severely limited mobility and helping her with a computer opened my eyes to the brain-dead and stupid interfaces supposedly intelligent programmers still design in the 21st century. Don't be like those people. Accessibility matters.
Last edited by Gerard Lally; 03-13-2017 at 07:26 PM.
Another thing: too often I have gone looking for your guides (setting up Slackware on online.net, for example) and found them missing, or at a new address.
Well, the project and the related documentation didn't jump fully-grown and armed out of Athena's head on day one.
- Hi guys. Here's 1.558 extra packages for Slackware. And dozens of pages of documentation. Have fun.
- Thanks. But we'd rather spend this whole thread explaining how we disabled JavaScript in our browsers.
- [...]
I have a lot of respect for you and your wonderful repository of packages, which I use.
That being said... this thread was created to announce a new website, not the 1558 extra packages for slackware that already existed, with the intent of asking feedback about it.
We did that, and you got upset about the criticism regarding a flaw in the fallback mechanism for browsers with no javascript active...
Like orbea said: if it was someone else most would probably not even bother to help.
Yes, we are trying to help. I'm sorry you don't see it that way.
But, if you are using NoScript, then press and hold the left mouse button on the center graphic and press delete, and then the same on the general overlay. Then you can use the site just fine without js. js is not required for this site.
Thanks for this information. I use NoScript and it worked just as you described. I wasn't aware NoScript could delete individual page components like this.
In the future I'll be trying this technique on stubborn web pages before I relent and temporarily turn on javascript for a domain or choose to skip the page.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.