Explore >> Select a destination
|
You are here 
|
tlrobinson.net | ||
| | | | |
dmitry.baranovskiy.com
|
|
| | | | | Personal web log of Dmitry Baranovskiy, web developer from Sydney, Australia | |
| | | | |
nolanlawson.com
|
|
| | | | | Here's a deep-in-the-weeds thing about web components that I ran into recently. Let's say you have a humble component: And let's say that this component throws an error in its connectedCallback: Why would it do that? I dunno, maybe it needs to validate its props or something. Or maybe it's just having a bad day.... | |
| | | | |
semicomplete.com
|
|
| | | | | Resig has a bunch of unit tests he does to make sure jQuery works properly on whatever browser. Manually running and checking unit test results is annoying and time consuming. Let's automate this. Update (May 2010): See this post for more details on automating xserver startup without having to worry about display numbers (:1, :2, etc). Combine something simple like Firefox and Xvfb (X Virtual Frame Buffer), and you've got a simple way to run Firefox without a visible display. | |
| | | | |
fak3r.com
|
|
| | | |||
