Webkit.js

#1

Post by ndesaulniers » Fri, Jun 20, 2014, 5:23 PM UTC

Webkit.js
trevorlinton.github.io

Re: Webkit.js

#2

Post by ozten » Fri, Jun 20, 2014, 5:27 PM UTC

FirefoxOS will host Safari / Chrome apps, before iOS will allow a Firefox.

Open FTW.

Re: Webkit.js

#3

Post by PLenz » Fri, Jun 20, 2014, 5:33 PM UTC

Anyway to get this to run in node with the output going to say Cairo? It'd be a fun little project to see if you could build a simple but working browser in nothing but JS.

Re: Webkit.js

#4

Post by atonse » Fri, Jun 20, 2014, 5:44 PM UTC

ozten wrote: post #2

FirefoxOS will host Safari / Chrome apps, before iOS will allow a Firefox. Open FTW.

What exactly are iOS users missing in Safari, in your opinion, that they would get from Firefox? I can see that Chrome has some cool sync features if you're into that sort of thing. But it still uses WebKit. And from what I've observed, people seem happy with the "Chrome" app in the app store, even though it uses a handicapped renderer. (Although in iOS 8, it won't be handicapped anymore, and will be as powerful as native Safari)

(Also WebGL support is new in iOS). Are people really clamoring for the Firefox engine to be supported in iOS?

Re: Webkit.js

#5

Post by LukeB_UK » Fri, Jun 20, 2014, 5:53 PM UTC

Getting errors on chrome 35.0.1916.153 on Linux Mint.

56 on line 34 in webkit.api.js

Uncaught # on line 15633 in webkit.bin.js

Re: Webkit.js

#6

Post by msvan » Fri, Jun 20, 2014, 5:56 PM UTC

PLenz wrote: post #3

Anyway to get this to run in node with the output going to say Cairo? It'd be a fun little project to see if you could build a simple but working browser in nothing but JS.

And then, getting the browser running itself in the in-browser browser.

Re: Webkit.js

#7

Post by dag11 » Fri, Jun 20, 2014, 5:56 PM UTC

I thought it was a static rendering, but then I put in a marquee tag and it moved flawlessly across the screen.

Impressive. I can't say I see the practical implementations of this, but I'm sure there's some. But it's impressive nonetheless.

Re: Webkit.js

#8

Post by pfraze » Fri, Jun 20, 2014, 6:02 PM UTC

dag11 wrote: post #7

I thought it was a static rendering, but then I put in a marquee tag and it moved flawlessly across the screen. Impressive. I can't say I see the practical implementations of this, but I'm sure there's some. But it's impressive nonetheless.

Rendering HTML to WebGL textures would be big, which I think this could do - though probably not as performantly as the browser could. It's currently not possible, partially due to security concerns if I remember right.

Re: Webkit.js

#9

Post by heydenberk » Fri, Jun 20, 2014, 6:03 PM UTC

It's a little contrived, but a "practical" use of this might be for an online HTML editor to embed the document (or display a preview) without any interference from the parent document.

Re: Webkit.js

#10

Post by schrodinger » Fri, Jun 20, 2014, 6:04 PM UTC

heydenberk wrote: post #9

It's a little contrived, but a "practical" use of this might be for an online HTML editor to embed the document (or display a preview) without any interference from the parent document.

You can do that via iframe as well