Dust provides asynchronous templates for the browser and Node.js.
browser
All posts tagged browser
The Chrome browser won’t be limited to Android devices and the desktop anymore. Google announced today at its annual I/O conference that Chrome is headed to iOS, and will be available on the iPhone later today, in fact.
Mozilla keeps cranking out the hits. Firefox 13 is here and brings with it a faster, smarter way of loading tabs, support for the SPDY protocol and plenty of other new tricks to keep Firefox fans happy.
Microsoft is looking for developers to help it build a “Skype for Browsers.” Think Facebook video chats without the need for Facebook.
Microsoft’s latest promotional effort for Internet Explorer takes a humorous look at the nerd fury it’s caused over the years.
Author: Tony Kroos
Posted: Thu Mar 01, 2012 9:03 pm (GMT -7)
Topic Replies: 1
Yes it is a normal behavior.
First, disable "Enhanced security" option in Browser object.
And do not run actions from tags directly, use function instead (you may pass parameters):
| Code: |
| <html> <body> <a href="#" onclick = "GoSub()">A sample link</a> </body> </html> <script type="text/javascript"> |
Author: dec
Subject: The [name] action cannot originate from a Web Browser link
Posted: Thu Mar 01, 2012 1:46 pm (GMT -7)
Topic Replies: 0
Hi there!
Take a look at this rare thing. In fact a possible workaround can be achieved, but, I want to know what do you thing, in other words, if is the normal and expected behaviour or not.
Supose we have a Web Browser object and use the "BrowserLoadFromStr" action to load this HTML and Javascript content:
| Code: |
|
<html> <body> <a href="http://www.neosoftware.com/">A sample link</a> </body> </html> <script type="text/javascript"> var el, for( var i = 0; i < els.length; i++ ) </script> |
Ok. The Browser show the HTML code with the "sample" link, and, when this link is clicked, the subroutine "BrowserLinkClick" is executed. No problem to here. Every work fine.
If we put on the subroutine NeoBook native actions, like "AlertBox" or something like that, again, all work like expected, the user click the link, the subroutine is executed, and the "AlerBox" actions too.
However, if we put on the subroutine a plugin action, for example:
| Code: |
|
:BrowserLinkClick .From PDF plugin pdfVersion "[Version]" Return |
… we get the error "The pdfVersion action cannot originate from a Web Browser link", somethin like this:
At a first instance I think this maybe is relation with some security issues, but, why we can execute native NeoBook actions from a Web browser object link, and cannot execute NeoBook plugin actions in the same way?
P.S. We are advised of this by a NeoBooker Friend, and, we found a possible workaround (not sure if work, but maybe yes), which consists to launch a Timer from the refered subroutine, so the Timer execute the needed actions, and then stop itself. Please, not considerer this as a big error or something, just a rare thing that get my curiosity. 
P.S.2. Here is a sample publication that show everything I say above.
_________________
SetVar "[NeoBookTvUrl]" "http://neobook.tv"
SetVar "[NeoPluginsUrl]" "http://neoplugins.com"
Among Silicon Valley developers, The Next Big Thing is Node. Node is short for Node.js, a new-age programming platform based on an engine at the heart of Google’s Chrome browser. It’s suited to building network applications that juggle scads of information streaming to and from other sources. In other words, it’s suited to the modern internet.
Browser makers have tapped everything from The Beach Boys to Godzilla to name their offerings. If you’ve ever wondered why Safari is named Safari or what Opera has to do with singers, we’ve got your answers.
Five to 10 years ago, the most powerful force in web browsing was the maker of the operating system — then, overwhelmingly Microsoft. Today, it’s the search and advertising engine — now, overwhelmingly Google.