|
|
|
| Authored by: PJ on Sunday, November 04 2012 @ 01:18 PM EST |
That's what I wanted to know, whether the resize
stuff was already there or created to subvert the
second order. From what you are saying, it was
not the latter. So that's good.
I didn't mean to post it. I meant to email it
to me, so I could look at the code, but since you
have done that, I'm satisfied.
It's important to always be fair and not assume
the worse, no matter whether you like or don't
like someone or some company. So I was reading
the possibilities and wanted to know for sure.
If you want to go the extra mile, you could
post the resize code in a plain
text comment.[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Sunday, November 04 2012 @ 02:58 PM EST |
The resizing code basically does a "screen height - X" for the main
display and seems to have appeared about a week ago.
The Heroresize function, contained in hero_resize.js is the one to check.
The value of X in the current code is 310 which is more than enough to hide the
message.
If the resize code previous to the correction was different (smaller) it would
point towards intentional rather than 'a happy coincidence".[ Reply to This | Parent | # ]
|
|
|
|
|
