That's what I'd have thought. I was thinking about it last night and couldn't
figure out how the server could compute this without the browser passing it
some extra information.
I'm glad this isn't the case as it took a couple of hours to write that article
and there's nothing worse than having it nullified by one simple line of code.
I just tested @BrowserInfo("JavaScript") and it still equates to "true" (1)
when JS is disabled, which makes it pretty useless really.
That's what I'd have thought. I was thinking about it last night and couldn't figure out how the server could compute this without the browser passing it some extra information.
I'm glad this isn't the case as it took a couple of hours to write that article and there's nothing worse than having it nullified by one simple line of code.
I just tested @BrowserInfo("JavaScript") and it still equates to "true" (1) when JS is disabled, which makes it pretty useless really.