mannix

5 ms·

1.
by mannix 13y ago
Second take: whhhhhaaaaaaaat native color pickers!!? That is really neat, must have missed that addition.
2.
by mannix 13y ago
Here's my take: this is very valuable on sites that dynamically load new pages without an actual browser navigation (read: pjax). It is not useful (and indeed it is an anti-pattern) for static sites in which case you'd want to jus
3.
by mannix 13y ago
True, its purpose is a port scanner, not a website scanner.
4.
by mannix 13y ago
Go to the Sources tab and click the || button to pause javascript. If you're wondering where the code is, just curl the URL :) (or, with Web Inspector open, refresh the page, go to the Network tab and select the only request.
5.
by mannix 13y ago
Probably to bust possible caching.
6.
by mannix 13y ago
It's fewer DOM manipulations from Javascript yes. The browser will still internally change the styles associated with the DOM elements, just without the JS overhead.
7.
by mannix 13y ago
(Rereading again..) The JS claim is silly. He is saying that because we are dynamically creating a single style, that show/hide logic will be faster. I disagree with this, since adding a CSS selector to the page means the page needs to
8.
by mannix 13y ago
You don't need to use javascript to hide/show matching elements. He also mentions something about it being faster than just an indexOf(), but gives no real benchmarks, so take that with a grain of salt.
9.
by mannix 13y ago
in js: console.log("\u062E \u0337\u0334\u0310\u062E")
10.
by mannix 13y ago
You can also cmd(right)-click on the titlebar, and choose a parent.
11.
by mannix 13y ago
No, but you can make it much more difficult by passing something like a frame of the game state, where some variables (like Timer) are passed in plaintext, and others (which are calculated in an aggregate way at runtime, e.g. can't be
12.
by mannix 13y ago
Table-based layouts will bite you down the road. Ever try to make a div that completely fills a td? Ever try absolute positioning in a table? It is tempting to use them because they are so simple and "just work", but they come wit
13.
Metasploit module & writeup for Firefox Tor exit node exploit(community.rapid7.com)
1 points by mannix 13y ago|0 comments
14.
by mannix 13y ago
Yeah, after you click a huge "VOID MY WARRANTY" button. I am surprised they made this change after the recent tor exit node exploit...
15.
by mannix 13y ago
Yes, the only reason I'd use __defineGetter__ would be a fallback for Object#defineProperty. I'm curious if the IE8 limitation could be worked around, using something like: if (ie8) RactiveBaseModel.prototype = HTMLA
16.
by mannix 13y ago
Crap. you're right. that's probably a dealbreaker.
17.
by mannix 13y ago
I have a question, since this has been bugging me with other js MV* frameworks lately... Is the set() method necessary for updating single attribute? All browsers have supported getter/setter APIs (__defineGetter__ and Object.definePro