news from many major sources in one spot, what do you think?

I see only 2 differences. Faster load time. Larger font.

No idea where to find the console.log for your site. Your directories are not accessible to me.

 

look this browser compatibility stuff is getting as annoying to me as it is to anyone expecting my site to just work...

so today i'll build something that captures the entire log,
sends it to the server in case the javascript doesnt fully boot up, and provides a simple message 'browser compatibility issue detected - developer has been emailed the relevant information'.

i'll also add a <noscript> tag.

please give me 1 to 3 days to properly code this in..
it'll also require a cleanup of my log and perhaps more log entries elsewhere.

i'll let you know in this thread when the changes have been uploaded.

and i do appreciate the help and criticism.

the console.log is kept in the browser, you can bring it up by calling up the debugger tools (in firefox and chrome that's done with the F12 key).

but like i said, i'll make something automated for it..

 

i've uploaded the changes that file a log of my own console messages, maybe it's enough to debug what's going on.

@sarahk @deathshadow

i'd appreciate it if the ones who couldn't view my site earlier, start it up again via http://seductiveapps.com/news(section'English_News') and let it run for 25 seconds, so that hopefully i see these logs appearing on my server. i did test the entire mechanism.

 

Your site failed to load up for me. I ran your site for more than 25 sec.

Why are you trying to fix this broken mess? Scrap it and build something different.

 

ok seems i have 2 sets of bugs to fix... that means i have to add debug info into the news app itself. and i will, later today.

about yesterday's bugs : i might have a fix online now. if the ones who provided me yesterday with the startup log would please try again and keep the window open for 25 seconds, that would be great. http://seductiveapps.com/news(section'English_News')

 

i now also added more debug info for the news app itself.

if the ones who couldn't load it, would please try again, and keep the page open for about a minute in total, that would be great.

http://seductiveapps.com/news(section'English_News__World_Headlines')

 

... and which of the 8 million console lines it continues to endlessly spit out every 32ms are you expecting to help you? Though your endless logging sure as shine-ola doesn't help the huffing memory footprint which is why in FF i have to manually kill the tab to stop it from hogging the system.

This might be a silly question, I've never needed to do this for anything since if your log is big enough to do this there's something WRONG with your code... but how exactly does one "Save the console log" -- not sure that's even a thing. Well, I can copy items to the clipboard one at a time in FF.

But again, you've got four digit megabytes of scripting doing double digits of CSS' job, so when it comes to things that you are doing in a manner that requires scripting -- like the CSR of content with no graceful degradation telling MANY users to go f*** themselves -- how you can even attempt to find an error is beyond me.

Even your layout code is broken banjaxed inaccessible bloated slow nonsense -- as evidenced by just your home page... which does nothing of value scripting off, uses javascript to do CSS flipping job, and wouldn't know accessibility, usability, or efficiency if they bit you in the arse.

You have a laundry list of how NOT to use web technologies, which is why your sites are broken useless trash to pretty much everyone who's responded here so far, or even just anyone with eyeballs.

I also may have found a contributor to why your site is such a painfully slow bloated mess in terms of handshaking. COOKIES. You're storing a shit-ton of data in cookies that is getting tacked onto the HEADER of every blasted file request! Given the nature of the data, you might want to consider using local storage instead of cookies -- that's what it's FOR. If the server needs to see it, send it an ajax state update and store it in sessions. That way you only need one cookie -- your session ID -- instead of many.

More cookies you use, slower the file access via http since again, cookies are tacked onto EVERY file request on that same domain.

 

received reports from a person using firefox 60.0 on windows 10, who tried getting in between 06:27am CEST and 07:16am CEST today,
and i had to add more debug info to see what exactly is going wrong. could you please try again? once or twice is enough by the way.

i have tested with firefox 60.0.2 on windows 10, and the entire website runs just fine. that's why i find this very strange, but i'm sure i can fix it with a few more bug reports that detail which parts of the code need to be made more robust.

the logs are sent automatically to the server when something goes wrong.
currently those events are:
- startup takes longer than 20 seconds (should take less than 5 really)
- news doesnt load up

why don't you just gracefully stfu just about now dude.

i spend a day catering to your paranoid attitude of having to be behind a VPN with a ping of 800ms per request,
i'm not going to spend a second catering to your css nazi-ism. your lack of gratitude, your trolling behavior towards anyone who doesn't use your particular code conventions, your continued attacks, it's all appearing very stupid.

i'm here for constructive criticism, not to be berated. you might wanna remember that.

and for the record : it's about 500Kb of minified javascript, including jQuery and other libraries.
that's about the same as a youtube player, or a facebook or twitter applet on a page.
stop lying about what's under the hood of my system.

 

Sorry if it's coming across as harsh, but you have some really neat ideas -- but your implementation is so painfully bad I really want you to understand just how absurd it is. IT's not "CSS-nazi-ism" to tell you that there's zero reason of a first-load to be blowing megabytes of scripting with nothing but CSR to do 48k of less of CSS' flipping job! It's biting you in the backside at every turn.

That FF access was probably me, let me open it up again, and I'm going to show you ANOTHER screenshot. Minified or no, it's too much scripting for the browser to be trying to execute! Even cache FULL with all the CSR and other scripting nonsense you're doing, execution time post-load is pushing upwards into half a minute!

Or not... can't show you a waterfall or breakdown since whatever your page is doing now, it's broken FF's document inspector and waterfall tools.

But it's 3.46 megabytes of JavaScript that is post gzip compression serving as 846k... and so much of that scrpiting reeks of "FOR WHAT?!?" since the page doesn't even finish loading.

I tell you wut, I'm going to recreate your home page as a static site, implementing every one of the primary layout controls like the hide/show of the content/footer areas, the click-through on the footer, and for laughs the body background chooser and login/register modals. I'll fix up the appearance to meet accessibility norms, and make it responsive whilst at it. I'll even create the code for the videos, though the blob:youtube one's won't work on my hosting since I'm not going to put this on a https domain.

The only thing JS should even be needed for to get the page that far is the tracking of selection changes in localstorage -- the layout controls and the background.

Before I even start coding, I would ballpark just that, with 5 paragaphs of lorem ipsum plugged into the content dialog, at:

HTML: 12k
CSS: 16k in one file (screen media only, I won't do print/others)
JS: 12k.

How much using your methodologies would you estimate JUST that much of your site at? I'm talking the entire code for that much of your functionality not even

Admittedly I'd probably axe the jerky unusable drop-down menus for modal dialog, particularly since you have the nice login and register modals...

I really want you to understand this because it's clear you're willing to put in a LOT of work, and I'd love to see what you could do if you could ditch the bloated frameworks, ditch the nonsensical "JavaScript for stuff it isn't meant for", and learn to write efficient code that at least attempts to meet accessibility norms.

If you could just learn to keep it in your pants on the JavaScript, with the amount of work it must have taken to get your page to this point with this much code, you would be RULING the Internet by now. You're the only person using JavaScript this much this way right now that I wouldn't call "lazy" -- but your technique is just utterly banjaxed and hobbling what you make!

To think what you could accomplish given the amount of work you're willing to put in if you could just stop using 100 times the code you need to do the job!

-- edit -- the clock starts now, 07:12 AM EST. Back in about an hour. (thankfully my plate is empty)

 

This might be a silly question but, is your code written in a manner that it dies if something like Ghostery tells your tracking scripts and adverts to suck it?

 

... and back. Elapsed time wow, an hour on the nose. Admittedly I was only able to belt this out so quick by lifting code from some of my other projects.

http://www.cutcodedown.com/for_others/seductiveApps/rewrite/

Same concept as your home page, but normalized for logical document structure, separation of concerns, letting CSS handle 99% of layout concepts like it should, implementing the background setting, content/footer area show/hide, footer click-through with a control to make it re-show (just the disclaimer, not the cookie agreement), top slide-in modal dialogs for the login and register functions, an example modal dialog for the background selection showing it as a proper gallery...

... and the background selections are even created using a JSON file, with it all tracked in local storage instead of cookies.

I also added a control to kill the "content area has its own scrollbar so shrink to fit" since that pisses off a lot of users. There's a reason you don't see normal websites pulling that stunt.

Mind you, no 'styled' scrollbar but honestly styled scrollbars are inaccessible slow crap. There's a reason all the different ways browsers offered doing that have NEVER been accepted by the W3C. Though if I WERE to implement it I'd probably use the ::webkit flavor in the stylesheet.

... and really IF I were to have the page customizable for dialog borders, backgrounds, etc, etc, I'd do it by either specifically manually loading extra stylesheets as an override, or by creating a new styleset in the scripting. (would be easier for the backgrounds than manually targeting dialogue elements for images).

Aka not even another 10k of JS.

Do you see what I'm saying, and how much faster/smoother/usable the result? It's by no means a perfect 1:1, but it works in FF and Chrome perfect, and edge "after a fashion"

NOT that any of this is really 'viable' in IE11/earlier. NOT that we should care at this point -- that's when you just let it gracefully degrade with its own stylesheet. (one of the few times I'd use X-UA, to force IE CC's back into working on 11)

In any case, the totals are:
HTML: 8.27k
CSS: 14k
JS: 9.41k
JSON: 1.86k

Well within my predicted sizes. THAT'S what I'm talking about... and why all that "loading" screen garbage you have should serve no real purpose.

... even when mine has a loading screen for JSON and thumbnail caching with an entire off-screen caching model in place. It just usually goes by so quickly you'd barely ever see it in the current usage.

 

Oh also notice accesskey 'd' and 'v' are functional. ctrl-shift+key in Firefox, alt+key in nearly any other browser, NO SCRIPTING NEEDED.

oh wait, alt+v has a conflict with existing shortcuts in Chrome... this is what's wrong with accesskeys, not the concept, but the implementation.

-- edit -- just remapped them to 'safe' accesskeys.

 

well good for you.. however your stuff doesnt do nearly as much as mine can do. no custom scrollbars, no way to select via that menu what dialogs are shown on the page (and then animating those into sight), no facilities for apps plugged into specific divs and then decorated along theme files, the list goes on and on and on.
i'm also getting like 1 startup bug report per day, and plenty of browse-throughs in my google analytics view.
this bug report was for FF60.0 on Windows 10, so i then installed the specific browser FF 60.0 on a windows 10 home laptop that i have, and my site loads up within seconds on that thing.

so i'm going to ask that person to upgrade their browser and try again.
i have no way of properly tracking this bug on that particular system.
not unless i litter my code with error handling code it doesn't need on the vast majority of systems requesting my page.

 

I just tested out @deathshadow's code.

I like the login/register drop downs - much better than most logins on most sites.

I also like the background change popup and how it works. Very simple. Very clean.

For a quickie-slapped-together site is definitely is better than the OP's site which simply does not work. Based on the screenshots in the thread @deathshadow's version looks like it may do the same thing much much faster and cleaner, although it does have a few minor problems, likely because of the speed of development.

The single biggest plus is that it WORKS!!!

 

went to the apple store, it works on all of their products.

also tested and verified to work : FF on windows 10, IE on windows 10, Chrome on windows 10, FF and Chrome on ubuntu, Chrome on android

and thanks to someone from a GMT-0400 timezone, i now know that my news app data retrieval needs to adjust the timezone to load up results. it does so now.