Primenet web design

[James Heinrich]

Originally Posted by Madpoo

Batalov just PM'd George and I about a similar error when doing a submit.

It was his submission that clued me into the errors that I fixed. But I can't fix the problem in 0.95_database.inc.php since that's George's domain.

I inadvertently "stole" credit for submitting his factor for M32057 when testing the submission, if someone wants to twiddle the database. There is another factor for M31481 awaiting submission for when the problem is fixed.

[Prime95]

Originally Posted by James Heinrich

@George: I just fixed some undefined errors in the code I added a couple days ago, but I've run into this when inserting a factor of unknown origin

My initial guess is that the call you just added to manual_post_processing wasn't quite right. Have a look at that and step through manual_post_processing, both of which should be in the www/manual_result directory and not in 0.95 PHP code.

[Mark Rose]

.

[James Heinrich]

Originally Posted by Prime95

My initial guess is that the call you just added to manual_post_processing wasn't quite right.

I've worked around the problem by initializing t_user to the anon_user[2] if there's no currently-logged-in user submitting the results and the user can't be found from the result line.

The other factor he found was now (after the above code change) submitted and properly credited to Batalov this time. If it's easy for you, please change the userid for 3266726955200737164011629254842087 on M32057 from "James Heinrich" to "Serge Batalov".

[garo]

http://www.reddit.com/r/javascript/c..._right/cqn8vpn

Why is this difficult?
Because it's not a blog full of content - it's a revolutionary interactive animated graphical UI paradigm which merely happens to deliver textual content to users.
They aren't really on your site to read your article or check what time their train leaves - they're really there to marvel at your buttery-smooth, hardware-accelerated 60fps animations and 1337 client-side javascript skillz that mean you can browse the entire site without ever once touching the server after the first page-load... just as long as you don't mind that first page-load being 3MB in size, crapping out on unreliable mobile connections and taking whole seconds between DOM-ready and the UI actually appearing.
But it's ok, because the ToDo app I wrote to test this approach performed pretty well with just me and my mum using it, and I don't care whether Google indexes it or not or whether blind people can see it because fuck them - they should just get some eyes, amirite?

[TObject]

Dear Poo,

The mersenne.org is currently using self-closing tags on non-void HTML elements. Some browsers treat those as open tags instead. You should change from:

<script type="text/javascript" src="http://ajax.aspnetcdn.com/ajax/jquery/jquery-2.1.1.min.js" />

To:

<script src="http://ajax.aspnetcdn.com/ajax/jquery/jquery-2.1.1.min.js"></script>

And all the other similar self-closing script tags too.

HTH

[Mark Rose]

Since disk space is cheap now, when someone is doing duplicate TF work, why don't we store the submitted results?

For instance, some of the TF work done on 79299719 doesn't give ranges, so I decided to rerun the TF work to 72. While I don't expect credit it for it, it would be useful to store lines such as

no factor for M79299719 from 2^1 to 2^67 [mfaktc 0.21 75bit_mul32_gs]
no factor for M79299719 from 2^67 to 2^68 [mfaktc 0.21 barrett76_mul32_gs]
no factor for M79299719 from 2^68 to 2^69 [mfaktc 0.21 barrett76_mul32_gs]
...

to show that the TF work was double checked.

[Madpoo]

Originally Posted by TObject

Dear Poo,

The mersenne.org is currently using self-closing tags on non-void HTML elements. Some browsers treat those as open tags instead. You should change from:

<script type="text/javascript" src="http://ajax.aspnetcdn.com/ajax/jquery/jquery-2.1.1.min.js" />

To:

<script src="http://ajax.aspnetcdn.com/ajax/jquery/jquery-2.1.1.min.js"></script>

And all the other similar self-closing script tags too.

HTH

That's funny because when I was doing the updates to the site, I ran it through a validator and although I know there are some funky things, that one in particular seemed a little iffy as to what it should be. Maybe I didn't consult enough sources at the time. Any idea what browsers would do such a horrible thing? Without jquery there are some table related fun things that won't work. I think the table sorting javascript relies on jquery... I don't remember now.

[Mark Rose]

Originally Posted by Madpoo

That's funny because when I was doing the updates to the site, I ran it through a validator and although I know there are some funky things, that one in particular seemed a little iffy as to what it should be. Maybe I didn't consult enough sources at the time. Any idea what browsers would do such a horrible thing? Without jquery there are some table related fun things that won't work. I think the table sorting javascript relies on jquery... I don't remember now.

Most browsers?

Since the script tag can contain other tags (for JS-disabled content), it can't self-close, much like a div tag. This has always been the HTML spec. I guess some browsers guess at closing it when they encounter a closing tag for the parent element, just like an unclosed em or strong tag.

However, any tag can be self-closing in XHTML, because that's a feature of XML in general. To trigger XHTML parsing, the HTTP headers must indicate a Content-Type of application/xhtml+xml. Decent browsers will then strictly interpret the content as well-formed XHTML, dying on any error, and IE will helpfully offer to save the document instead of rendering it.

XHTML never went anywhere because many developers can't produce valid HTML let alone valid XML and rely on sloppy parsing (IE's tolerance of sloppy code made this practice wide spread, especially when IE became the dominate browser in the late 90's). XHTML also prohibits inline JavaScript, so you can't do things like Document.write, which broke a lot of ads and whatnot.

I once wrote an interactive site that generated XHTML about five years ago. It used user-agent sniffing to change the mime-type to text/html for IE, and in the other browsers, it rendered in milliseconds since the parsing was so much faster (all the images also had defined sizes, so there were zero reflow/repaints). I doubt I'll ever do it again :)

[TObject]

jQuery actually works, as it is the first of such tags. It is scripts following a self-closed tag that may suffer.

Firefox for Windows 37.0.2, for example, never loads the /scripts/apy5/menu.js?v=20140927.1 script from the home page. Where Internet Explorer 11 does so.

[Madpoo]

Originally Posted by TObject

jQuery actually works, as it is the first of such tags. It is scripts following a self-closed tag that may suffer.

Firefox for Windows 37.0.2, for example, never loads the /scripts/apy5/menu.js?v=20140927.1 script from the home page. Where Internet Explorer 11 does so.

Figures.

Okay, okay, mercy. I just changed it.