2018-03-25 6:29 GMT+02:00, Roger Hågensen :
> On 2018-03-24 22:32, Andy Valencia wrote:
[...]
>> We're all well aware of the behaviors which make browsers adopt such
>> defensive measures. Are we looking at enough use-cases to think about
>> some
>> sort of general
If this problem is specific to the "track a route" use-case, and the
use-case is sufficiently widespread, would a dedicated "route recording"
API make sense?
E.g., a web page could ask the browser to continously record location
changes and - at some time at the browser's discretion - push a list
As the IETF usecase seems to be about permalinks, is there any requirement
for rel=canonical regarding validity in the future?
Am 06.08.2017 3:20 vorm. schrieb "Kevin Marks" :
> That use case sounds more like rel="canonical"
>
> On 6 Aug 2017 2:07 am, "Ed Summers"
Paving the cowpaths is all well and good, but if it ends up recommending
technologies which unilaterally favor some parties, that sounds like a big
argument to develop a better technology.
Mark Kaplun schrieb am Mi., 26. Juli 2017 um 17:07 Uhr:
>
> [...]
>
> As far as I know,
Mark Kaplun schrieb am Mi., 26. Juli 2017 um 15:43 Uhr:
> [...]
> Basically the HTML is loaded first, and at some point you can have some JS
> that will load the JSON by an AJAX request. google is happy to get the
> JSON-LD this way [...]
>
This sounds like an interesting
ber FastBoot etc..)
Did you mean to reply to the group, or only to me?
On Mon, Jul 24, 2017 at 11:30 AM Philipp Serafin <phil...@gmail.com> wrote:
> Because it's annoying for human users if there is too much information
> cluttering up the page that is nor relevant in the current context.
If I see this correctly, we're currently talking about two different
use-cases for file/directory access:
1) Giving HTML apps the ability to "open" and edit local user-provided
files and directories in a similar manner to desktop apps (the soundboard
example)
2) Loading (parts of) the app itself
Domenic Denicola schrieb am Di., 11. Apr. 2017 um 18:01 Uhr:
> From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of
> Patrick Dark
>
> Bingo. This mailing list is for developing technology for the world wide
> web, not for peoples' local computers.
>
Doesn't that
Patrick Dark schrieb am Di., 11.
Apr. 2017 um 13:55 Uhr:
> [...] The only good reason to distribute an application this way is
> because you want it to be confidential [...]
>
Another use-case would be to develop a HTML app that does not require
internet
Note also that the HTTP server solution requires you to ship a binary (the
server) with your files, therefore sacrificing platform independence and
requiring the user to run an untrusted binary, all just to show some HTML
files.
Jonathan Zuckerman schrieb am So., 9. Apr.
I admit, I haven't really followed this debate. But out of interest: Is
it by now actually possible to write any kind of implementation that
complies to both, the HTML5 *and* the RDFa specification?
Regards,
Philipp Serafin
Am Dienstag, 2. August 2011 19:32:52 schrieb Ian Hickson:
On Tue, 2
link
location/copy image location etc. Maybe links/images with post-data
could be treated like input elements regarding their context menu.
Regards,
Philipp Serafin
On 09.12.2010 20:04, Ashley Sheridan wrote:
On Thu, 2010-12-09 at 11:01 -0800, Adam Barth wrote:
We've seen use cases for a similar
On 09.12.2010 20:41, Philipp Serafin wrote:
On 09.12.2010 20:04, Ashley Sheridan wrote:
It makes sense in the case of a link like that, as it is changing
some state on the server, which is what POST data was intended to do.
If images are called with POST data, then that would prevent them
their avatar once when they register,
though a few may change them based on mood, holidays, etc.)
Regards,
Philipp Serafin
be mobile devices that really have nothing even
remotely comparable to a printing functionality. For those, it could
make sense to hide print this page links to provide more screen real
estate.
I admit though, that's a rather esoteric use case ...
Regards,
Philipp Serafin
timeless schrieb:
On Thu, Dec 25, 2008 at 8:29 PM, Philipp Serafin phil...@gmail.com wrote:
Well, you could still phrase it something along the lines of The size of a
popup document's viewport SHOULD be calculated using the CSS shrink wrap
algorithm... etc etc.
as an embedder
Filippo Levizzani schrieb:
hey Giovanni,
merry xmas and happy new year! :)
Filippo
Indeed! Frohe Weihnachten und einen Guten Rutsch ins Jahr 2009!
Regards,
Philipp Serafin
Ian Hickson schrieb:
On Thu, 18 Dec 2008, Philipp Serafin wrote:
I think it would be a good idea to spec this algorithm as well then.
The algorithm I described is basically CSS' shrink wrap algorithm. But
we can't really require it, as it assumes that the OS has windows. My
desktop
dialogs to specify font
settings, etc. The HTML in the dialogs could be displayed in a
normal-sized browser window effortlessy. However, it would look pretty
silly.
Regards,
Philipp Serafin
Ian Hickson schrieb:
On Thu, 27 Nov 2008, Anne van Kesteren wrote:
On Mon, 24 Nov 2008 18:46:51 +0100, Philipp Serafin phil...@gmail.com wrote:
I guess this is more a cosmetic remark, but I thought I'd bring this up
anyway.
I've noticed that the paragraph on the MetaExtensions wiki
Ian Hickson schrieb:
On Thu, 18 Dec 2008, Philipp Serafin wrote:
There is no reasoneable default size the page could adjust to. If the
author can't specify the size of a popup/dialog, what algorithm should
the UA use to find out the correct optimal size?
Lay out the page at infinite
been changed
to ... or must be defined by a W3C specification in the Candidate
Recommendation or Recommendation state. some time ago.
Shouldn't both paragraphs be identical, or are @rel and meta values
really handled differently?
Cheers,
Philipp Serafin
[1] http://wiki.whatwg.org/wiki
Thomas Broyer schrieb:
On Mon, Nov 17, 2008 at 3:03 AM, ddailey [EMAIL PROTECTED] wrote:
4. Concerning the first thing I need to fix, I am not sure if HTML5
currently provides a solution for. Here's the sitch: because of an extensive
use of CTRL sequences in the interface, the user will
On Wed, Nov 5, 2008 at 4:00 PM, Leons Petrazickis
[EMAIL PROTECTED] wrote:
It matters in the sense that web browsers would have to implement both
approaches for backwards compatibility.
This depends what you mean when talking about implementing a tag.
Browsers already load all tags and
On Tue, Oct 28, 2008 at 9:27 PM, Eduard Pascual [EMAIL PROTECTED] wrote:
[The best] solution I can think of this would be an additional pseudo-class,
such
as :default, :initial-value, :non-modified, or anything like
that (I'm really bad at naming stuff, so please take those only as
On Wed, Oct 22, 2008 at 2:07 PM, Fabien Meghazi [EMAIL PROTECTED] wrote:
The goal would not be to completely forbid canvas but to block it by
default while allowing the user to activate it when he wants to.
This is a nice feature to have, but the problem is, would it work in
reality? It works
On Sun, Oct 19, 2008 at 2:57 PM, Håkon Wium Lie [EMAIL PROTECTED] wrote:
I'd like to have a simple way of using button along with a to
create pretty links. This markup works in Opera, Mozilla, and Webkit:
a href=http://www.w3.org/;buttonW3C/button/a
but it's not valid HTML5 it seems. I
thinking out loud
Just had a thought (no idea how original) -- how about if fillStyle were
able to accept a 3 or 4 number array? eg. fillStyle = [0, 0.3, 0.6, 1.0] ?
That might work well if people are using arrays as vectors/colours
/thinking out loud
Instead of an array, we could also use
, it's not like the other technologies would vanish all of a
sudden. If you have sufficient control over your server, you can STILL
use Java or Flash sockets.
Regards,
Philipp Serafin
Please correct me if I'm wrong here, but it looks to me as if RDFa
uses namespaced identifiers nowhere outside attribute values right
now. So couldn't you just introduce a rdf specific namespacing
system for example like eRDF does[1]? This way, RDF parsers could
still look up metainformation about
On Sun, Jul 27, 2008 at 8:44 PM, Russell Leggett
[EMAIL PROTECTED] wrote:
Hi all,
I checked through the archives, but did not see anything, so if this has
been addressed already, I apologize.
This is a suggestion that is more helpful to larger single page web
applications, but could also be
with HTTP.
If desired, maybe we could add an API to XHR to control pipelining though?
Regards,
Philipp Serafin
. Java
applets can already do pure TCP connections to the server they are
hosted on, and I have never heard of the type of attack that you
describe above.
Regards, Frode
Regards, Philipp Serafin
On Fri, Jun 20, 2008 at 1:19 PM, Frode Børli [EMAIL PROTECTED] wrote:
I think this will be a far better solution than opening a second
communication channel to the server (ref my other posts).
Would that be so much of a problem though? Your web application opens
multiple connections today
On Fri, Jun 20, 2008 at 7:31 PM, Frode Børli [EMAIL PROTECTED] wrote:
If the socket is created like this: var socket = new
WebSocket(http://www.example.com/chatserver.xsocket;);
Then the .xsocket file is an XML file specifying exactly how the
WebSocket should connect to the server and perhaps
Still I do not believe it should have a specific protocol.
I think a major problem with raw TCP connections is that they would be
the nightmare of every administrator. If web pages could use every
sort of homebrew protocol on all possible ports, how could you still
sensibly configure a firewall
down to a trickle.
What do you think?
With best regards,
Philipp Serafin
There's no need to request things more than once -- I base my editing
decisions on the quality of the arguments put forward, not the quantity.
By all means, if you have new information, bring it forward, but merely
repeating what has already been said doesn't do anything.
I'm sorry. I missed
I'd like to plug the approach with MIME parameters again, because it
seems by far the most elegant and clean to me.
However, instead of specifying multiple sizes in one MIME parameter,
couldn't we just define two parameters width and heigth (and
perhaps a ratio for graphics without inherent
39 matches
Mail list logo