to scripting or other content loading mechanisms,
unless explicitly enabled by an access control mechanism.
]]
It think we should move it out of PC into the API spec or some other spec.
Kind regards,
Marcos
the ability to view or otherwise link to the
referenced license.
]]
I don't know if we should delete them, or move them to another spec.
Kind regards,
Marcos
it to:
[[
Note: A user agent that supports the [Widgets-APIs] specification will
expose any declared preference to the author at runtime via scripting in
the manner described in the [Widgets-APIs] specification.
]]
Kind regards,
Marcos
]
I presume the example is in error.
The use of widget.preferences[key] is correct.
--
Marcos Caceres
http://datadriven.com.au
On Wed, Aug 19, 2009 at 1:41 PM, Bjoern Hoehrmannderhoe...@gmx.net wrote:
* Arthur Barstow wrote:
On August 18 a Last Call Working Draft of the Widgets: APIs and
Events spec was published:
http://www.w3.org/TR/2009/WD-widgets-apis-20090818/
As Marcos noted at [1], the title is misleading
, not in the
spec.
Try it out in Firefox's address bar:
javascript: localStorage.setItem(test, test123);
javascript: alert(localStorage[localStorage[0]])
javascript: alert(localStorage.test)
The above will alert you test123
--
Marcos Caceres
http://datadriven.com.au
are as follows:
Fixed.
I'll check in a new draft later today.
--
Marcos Caceres
http://datadriven.com.au
that.
--
Marcos Caceres
http://datadriven.com.au
,
Marcos
--
Marcos Caceres
http://datadriven.com.au
discussions about Web
Storage to public-webapps (as the work is supposed to be taking place
in this working group). Selfishly, Widgets have a dependency on that
spec, so some of us here need to be kept up-to-date :)
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
On Thu, Aug 20, 2009 at 2:26 PM, Marcos Caceresmarc...@opera.com wrote:
...seems a recent change to Web Storage may be even more serious.
Someone just told me that the Web Storage spec has changed to allow
storage of things other than strings. Need to confirm that.
To overcome changes
Hi, I've renamed the AE spec to:
Widgets 1.0: The widget Interface
If anyone has a better name, then please let me know.
You can see the title in all its glory here:
http://dev.w3.org/2006/waf/widgets-api/
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
Ian Hickson wrote:
On Thu, 20 Aug 2009, Marcos Caceres wrote:
I recently noticed some substantial changes to Web Storage (allowing
things other than strings to be stored).
Did the discussion to make such a change happen on the web-apps working
group's mailing list? If yes, please disregard
On Thu, Aug 20, 2009 at 11:16 AM, Marcos Caceresmarc...@opera.com wrote:
The lack of review should be obvious from the errors in nearly all the
examples: in 6.5.1 it uses made-up schemes without pointing that out in
any way,
They are not made up? - only feed does not have a spec! Specs below
like to proceed with these editorial changes asap (e.g. have it done
before our next telco), and I just would like first to consult with the group
whether there are any objections or comments wrt the above modifications.
As far as I am concerned, go forth and spec! :)
--
Marcos Caceres
http
On Tue, Aug 18, 2009 at 1:27 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi Marcos,
Thanks for your comments.
Can we just call it view-mode?
Again, just viewMode
Actually I was thinking about it and got stick to the widget environment with
view modes due to the following
On Tue, Aug 18, 2009 at 2:37 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi Marcos,
It seem to get an off-topic discussion...
Apologies; I rushed my responses.
Do we care about non-widgets using view modes?
Of course not :) The technology should be generally applicable where
/widgets/Overview_TSE.html#the-author-element
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
. Anyone with experience, please take a look.
Please also consider this a first draft and contains errors; I'm
totally open to suggestions as to how to proceed here.
http://dev.w3.org/2006/waf/widgets/Overview_TSE.html#prologue
Kind regards
Marcos
--
Marcos Caceres
http://datadriven.com.au
Hi Simon,
On Thu, Aug 13, 2009 at 7:45 PM, Simon
Harpersimon.har...@manchester.ac.uk wrote:
Hi there Marcos, sorry for the delay in responding - I've been thinking
about this...
It seems to me that the current aspects of accessibility and notification is
built in general for content, yet we
On Fri, Aug 14, 2009 at 12:21 PM, Simon
Harpersimon.har...@manchester.ac.uk wrote:
Hi there, thanks for this.
On 14 Aug 2009, at 10:12, Marcos Caceres wrote:
Hi Simon,
On Thu, Aug 13, 2009 at 7:45 PM, Simon
Harpersimon.har...@manchester.ac.uk wrote:
Hi there Marcos, sorry for the delay
On Thu, Aug 13, 2009 at 2:31 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi Marcos,
Thanks for your comments.
Which developers in particular did you have in mind?
I meant developers who could develop widgets by hand, without any
automation.
(These may the same people as here
Simon Harper wrote:
Great, so that clears up some parts of my misunderstanding of the widget
spec. I thought that the spec, as is, would form a series ending up at
UI and therefore we would be able to contribute at an early stage.
Heh, we actually started this working group four years ago
On Mon, Aug 10, 2009 at 1:36 PM, Scott
Wilsonscott.bradley.wil...@gmail.com wrote:
On 10 Aug 2009, at 10:00, Marcos Caceres wrote:
Secondly, although some elements are not exposed as part of AE (e.g.,
icon and license), there are still conformance requirements as to how
the user agent
Marcin Hanclik wrote:
Hi Marcos,
Thanks for your comments.
I think we should ask i18n for guidance.
Let's ask them.
To Step 7, I've added If doc is encoded in a format that is
unsupported by the user agent, then the user agent must terminate this
algorithm and treat this widget package
Marcin Hanclik wrote:
Hi Marcos,
Thanks with remark:
1. deleted the PC's ABNF definition of utf8-char.
OK.
2. added The utf8-char rule is defined in section 4 of [UTF-8].
I think it needs further refinement, since section 4 of [UTF-8] is for the full
range of utf-8, i.e. starting
it is better for a conformance checker to
inform the author when they have used features not supported by the
specification, but not to put such restrictions on UAs.
[1] http://www.w3.org/TR/widgets/#rule-for-verifying-a-file-entry
--
Marcos Caceres
http://datadriven.com.au
regards,
Marcos
Jeremy Orlow wrote:
On Fri, Jul 31, 2009 at 1:52 AM, Marcos Caceres marc...@opera.com
mailto:marc...@opera.com wrote:
Keeping in line with the design goals to enable Widget-related
technologies to be used on the Web, I'm wondering if we should spawn
a separate specification
On Tue, Jul 28, 2009 at 12:04 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi Marcos,
Unless it's broken (?), I would prefer to leave it as is.
I think that PC should either change the grammar (as suggested in my email)
or specify that the zip-rel-path operates on characters
2009/7/25 Marcin Hanclik marcin.hanc...@access-company.com:
Hi Marcos, All,
Regarding the usage of IRI in the widget configuration document, I do not
know which speicification is responsible for mandating the IRI normalization.
It is possible that I simply have not yet found the proper
On Tue, Jul 28, 2009 at 12:27 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi Marcos,
Yeah, that seems reasonable. I've added it.
I have not seen your change, I do not know where to look for it.
See http://dev.w3.org/2006/waf/widgets/Overview_TSE.html#iri-attribute
Anyway, I
On further consideration, Opera has decided this is not a bug. We
would like to leave the behavior as is in the spec. What do others
think?
On Fri, Jul 31, 2009 at 5:50 PM, Marcos Caceresmarc...@opera.com wrote:
Opera QA has found the following bug in the Widgets 1.0: Packaging
about a better way of doing this, we
would certainly like to hear it.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
to have occurred.
Thoughts? Or have I answered my own question (don't test with the AE
spec! :) )?
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
Hi Robin,
Thanks for putting this spec together... I copy/pasted the spec below
and added inline comments.
Enjoy! :)
On Thu, Aug 6, 2009 at 9:53 PM, Marcos Caceresmarc...@opera.com wrote:
1 Introduction
User agents running widgets are expected to provide access to
potentially sensitive APIs
On Tue, Aug 4, 2009 at 3:02 PM, Dominique Hazael-Massieuxd...@w3.org wrote:
Le vendredi 31 juillet 2009 à 18:01 +0200, Marcos Caceres a écrit :
I've created the first draft of the test suite edition, it is
available here (it's ugly on purpose, I will remove the ugly
stylesheet soon):
http
As a followup to the above, the following code was submitted by Google
to WebKit to support notifications:
https://bugs.webkit.org/show_bug.cgi?id=25463
So, the question is: do we need a new/separate spec? One that covers
both Web and Widgets?
Kind regards,
Marcos
[1] http://dev.w3.org/2006/waf
in this algorithm below, and move onto the next range.
[1] http://www.w3.org/TR/2009/CR-widgets-20090723/
--
Marcos Caceres
http://datadriven.com.au
the MIME type formally registered)?
--
Marcos Caceres
http://datadriven.com.au
happily live separately from
each other. Those view types seem to serve practical roles/patterns,
while W3C view modes are more like states of being/rendering states...
so, a W3C mode can be in any view types listed above (e.g., fullscreen
home, floating profile, etc.).
--
Marcos Caceres
http
characters.
The above grammar seems to allow 0080-10 (the UTF-16 accessible range
minus characters 0080)
http://tools.ietf.org/html/rfc3629#section-3
whereas the current utf8-char rule is more selective.
Unless it's broken (?), I would prefer to leave it as is.
--
Marcos Caceres
http
2009/7/25 Marcin Hanclik marcin.hanc...@access-company.com:
Hi Marcos, All,
Regarding the usage of IRI in the widget configuration document, I do not
know which speicification is responsible for mandating the IRI normalization.
It is possible that I simply have not yet found the proper
as those of the same attribute on
feature. I think it makes sense to be consistent here.
Marcos
I can live with this if the rest of the WG wants it,
but I don't get the sense this will get used much (i.e., required = false').
So again, do we _REALLY_ need this?
Bryan
In the case of the resources
On Tue, Jul 21, 2009 at 7:40 PM, Marcos Caceresmarc...@opera.com wrote:
On Jul 21, 2009, at 7:27 PM, Scott Wilson scott.bradley.wil...@gmail.com
wrote:
+1
Sounds sensible - I've had a hard time figuring out what to do about these
without the view modes spec being completed.
I guess
,
Marcos
--
Marcos Caceres
http://datadriven.com.au
can add them as supplemental to the Widget object:
[Supplemental] interface Widget {
readonly attribute DOMString viewMode;
attribute ModeChangeListener onmodechange;
};
Moving them will allow AE to be finished more quickly.
Kind regards,
Marcos
--
Marcos
that they can conform to AE
S
On 21 Jul 2009, at 17:32, Marcos Caceres wrote:
I think we should remove onmodechange and viewMode from the AE spec
and move them to the View modes spec (View Modes defines
ModeChangeEvent already!). Those attributes are currently
underspecified in AE and can't
() methods.
B. upon the attempted invocation of the clear() method, a user
agent must not remove the key-values of the protected preference from
a storage area.
WDYT?
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
sense from a Wookie perspective.
For more detailed arguments for keeping preferences, just search back
through the list ;-)
(We've already argued this one loads of times, Marcos! Why has it come
up again?)
I guess it helps me understand the problem and articulate use cases...
need a Wookie
On 7/20/09 4:45 PM, Robin Berjon wrote:
On Jul 20, 2009, at 16:08 , Marcos Caceres wrote:
In the widgets API spec, what are the advantages of having a
widgets.preferences attribute when the window.localStorage is already
available on the window object?
I think we should:
1. Drop
: http://getfeedforward.org
Wookie: http://getwookie.org
scott.bradley.wil...@gmail.com
http://www.cetis.ac.uk/members/scott
--
Marcos Caceres
http://datadriven.com.au
On Thu, Jul 16, 2009 at 1:36 PM, David Rogersdavid.rog...@omtp.org wrote:
Art, Marcos,
Please could you give us an update on the status of the progression of
Widgets PC to CR?
The editor's draft will be the one that is published (it is stable and
ready to go, and has been for a few days):
http
On Thu, Jul 16, 2009 at 1:53 PM, Marcos Caceresmarc...@opera.com wrote:
On Thu, Jul 16, 2009 at 1:36 PM, David Rogersdavid.rog...@omtp.org wrote:
Art, Marcos,
Please could you give us an update on the status of the progression of
Widgets PC to CR?
The editor's draft will be the one
On Wed, Jul 15, 2009 at 1:54 PM, Jean-Claude
Dufourdjean-claude.dufo...@telecom-paristech.fr wrote:
Marcos Caceres a écrit :
From the spec ...an author can request that a widget asynchronously
check if a widget has been updated [(i.e., that a new version of the
widget package is available
, they are orthogonal. HTML5 UA, however, may implement web storage.
--
Marcos Caceres
http://datadriven.com.au
a chance to
respond and act, then, if you have concerns, raise them here.
Kind regards,
Marcos
On Sat, Jul 11, 2009 at 8:19 AM, Richard Ishidaish...@w3.org wrote:
Hi Marcos,
Without understanding why folks think these things, it's a little difficult
to provide specific discussion points, but the key point behind ITS is that
it describes types of information you need for a well
[http://www.w3.org/TR/2009/WD-widgets-20090528/#examples]
Comment:
The simple example in Section 7.2 still contains an error. The language tag
for Spanish is es, not sp. It is shown correctly in the graphic but not
the title of the section or elsewhere in the text.
Fixed. Thanks!
--
Marcos
this feature :)
--
Marcos Caceres
http://datadriven.com.au
editors' draft, the rightmost occurrences are removed (as
suggested above).
Please see for the updated algorithm:
http://dev.w3.org/2006/waf/widgets/#step-5--derive-the-user-agents-locale
--
Marcos Caceres
http://datadriven.com.au
are a super-set of URIs, so I did
not point out the difference.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
late:)).
Hi, Krzysztof!
Thanks again for the detailed review! Inline comments below...
2009/6/22 Krzysztof Maczyqski 198...@gmail.com:
Dear Marcos and WG,
Here follows my set of remarks on Widgets 1.0: Packaging and Configuration
which I hope you'll find valuable during LC review. It's based
. We'll review it.
Addison
--
Marcos Caceres
http://datadriven.com.au
are not simply fear driven. Is there some way that the Internationalization community can
support implementers?
The concerns are that people won't implement ITS (or that authors can
use the appropriate Unicode markers to achieve the same thing as ITS).
Kind regards,
Marcos
On Fri, Jul 10, 2009 at 5:20 PM, Marcos Caceresmarc...@opera.com wrote:
On Fri, Jul 10, 2009 at 4:40 PM, Phillips, Addisonaddi...@amazon.com wrote:
(personal response)
The WebApps WG believes that removing the redundant repetitions in
a
standardized way may avoid interop issues. Having said
On Wed, Jul 8, 2009 at 11:26 AM, Dominique Hazael-Massieuxd...@w3.org wrote:
Le mardi 07 juillet 2009 à 19:53 +0200, Marcos Caceres a écrit :
For the sake of the Disposition of Comments, please let us know if you
are satisfied with the fixes below (if possible, by the 9th of July).
I'm mostly
For the sake of the DoC, can you live with the current i18n model?
On Sun, Jul 5, 2009 at 12:45 AM, timelesstimel...@gmail.com wrote:
On Fri, Jul 3, 2009 at 7:35 PM, Marcos Caceresmarc...@opera.com wrote:
I talked to our localization guys about this, they said that is
definitely not a good
Hi Francois,
Just to be clear, I made the change you requested (relative and abs
URIs behave exactly the same). I think that concludes all issues
raised in this thread.
For the Disposition of Comments, can we get your acknowledgment that
you are satisfied?
Kind regards,
Marcos
On Tue, Jul 7
Accidentally forgot to send to public-webapps.
-- Forwarded message --
From: Marcos Caceres marc...@opera.com
Date: Wed, Jul 1, 2009 at 12:28 PM
Subject: Re: [widgets] Rule for Parsing a Non-negative Integer
To: Anne van Kesteren ann...@opera.com
2009/6/10 Anne van Kesteren ann
that this
is the way it's going to work for now.
--
Marcos Caceres
http://datadriven.com.au
?
--
Marcos Caceres
http://datadriven.com.au
and links in other files are mapped to widget
resources?
I agree. This should be consistent: the URI spec needs to follow the PC spec.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
On 7/6/09 4:47 PM, Robin Berjon wrote:
On Jul 6, 2009, at 16:07 , Marcos Caceres wrote:
On 7/6/09 3:35 PM, Robin Berjon wrote:
On Jun 30, 2009, at 11:24 , Marcos Caceres wrote:
The purpose of widget.update() is/was _not_ to update the widget in
any meaningful way:
(...)
In other words
On 7/6/09 12:45 PM, Thomas Roessler wrote:
This text assumes that widget installation is always an interactive
process. It might very well be part of batch processing, in which case
an interactive, localized error message might simply be the wrong thing
to do.
correct.
I'd suggest to
Hi Martin,
Inline comments below.
For the sake of the Disposition of Comments, please let us know ASAP
if you are satisfied with the working group's responses below (by
Thursday if possible).
On Mon, Jun 15, 2009 at 5:12 PM, Marcos Caceresmarc...@opera.com wrote:
Section 5.3: Why not mandate
Hi Francois,
On Mon, Jul 6, 2009 at 6:01 PM, Francois Daoustf...@w3.org wrote:
Marcos Caceres wrote:
Hi Francois,
A brief response to your question below...
For the Disposition of Comments, can you please respond to this email
and indicate if you are satisfied with the WG's responses
without an explicitly declared or inherited xml:lang
attribute.
And I've added another example to the Element-Based Localization
section, which talks about the behavior of xml:lang, how it is
inherited (as per the XML spec), and how that inheritance can be
overridden.
--
Marcos Caceres
http
a better QA process and we should not attempt
to solve this technologically.
Please see also Jere's feedback to your comments above in [2].
For the sake of the Disposition of Comments, can you live with the
current model?
Kind regards,
Marcos
[1] http://lists.w3.org/Archives/Public/public-webapps
is in error and the user agent must ignore it. Is this
not again stating what has already been stated? Duplicating requirements
makes the specification very hard to read.
Editorial: Agreed. This is no longer duplicated as the first assertion
has been removed.
--
Marcos Caceres
http
, can you live with the above definition?
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
legacy/proprietary widget types in order to conform to this
specification it must treat widget packages as according to this
specification.
Fixed.
--
Marcos Caceres
http://datadriven.com.au
. The UA
still does the right thing (it loads the index.svg file and finds it
is not well formed.)
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
to
implement (which in this case it is, but that is mentioned elsewhere).
--
Marcos Caceres
http://datadriven.com.au
.
7 minutes
4:52 PM me: ignore means that a user agent must act as if the element,
or fileis not present.
add a space between 'file' and 'is'
Fixed.
--
Marcos Caceres
http://datadriven.com.au
to cross
or wait, and in US there are orange and white lights.
What actually happened was that the text of the buttons changed
between maemo4 and maemo5 (as with the accept/reject buttons from the
iTunes example).
--
Marcos Caceres
http://datadriven.com.au
On Tue, Jun 30, 2009 at 10:27 AM, jere.kapy...@nokia.com wrote:
On 29.6.2009 13.30, ext Marcos Caceres marc...@opera.com wrote:
Right. I've moved everything and renamed examples Localization examples.
This would make the material flow better and have all the concepts defined
before
On 6/30/09 7:49 PM, timeless wrote:
On Tue, Jun 30, 2009 at 4:24 PM, Marcos Caceresmarc...@opera.com wrote:
Or use index.html in other directories?
Nothing. Treated as an arbitrary file - this was already implied in
the spec. To make this explicitly clear, I've added:
speaking of which
-user, and the wording of the
localized error message, is left to the discretion of implementers.
In the case the UA is a CC, it must inform the author that the Zip
archive is an invalid Zip archive.
]]
Is that any better?
--
Marcos Caceres
http://datadriven.com.au
of space characters (in any order)
with a single U+0020 SPACE character.
Functionally, I don't believe this change either algorithm, so this
will be treated as an editorial comment.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
). If no one implements it, then we
will remove it.
textContent is an attribute, not a property. In bindings it might turn into a
property, but that is not relevant I think.
Fixed.
--
Marcos Caceres
http://datadriven.com.au
the definition of file-extension _none_ of the entries in the
table would be matched. I.e. file-extension requires a leading dot.
Fixed.
--
Marcos Caceres
http://datadriven.com.au
2009/6/10 Anne van Kesteren ann...@opera.com:
I think the first paragraph here can be dropped as you cannot test it.
Optionally you could rephrase it as a non-normative note.
Changed this to a note.
--
Marcos Caceres
http://datadriven.com.au
On Mon, Jun 29, 2009 at 2:10 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi Marcos, All,
These are a few editorial comments to the latest PC ED.
6.6 Icons and 9.1/Step7/icon
Step7 requires only a valid path for src attribute:
Let path be the result of applying the rule
it works right now
and seem consistent with the way I would expect absolute paths to
work). However, I think I will defer this to the working group for a
resolution; others may agree with your position or I might not be
understanding your proposal.
Kind regards,
Marcos
--
Marcos Caceres
http
On Wed, Jul 1, 2009 at 2:04 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi Marcos,
I have found other typos:
Step 7, icon;
Let file the result of applying
Should be
Let file be the result of applying
Fixed.
6.6.2
A default icon is an reserved icon ...
Should
the UA to choose the best icon?
Yes, it's up to the UA, but you still need to search for them in the
right order. Searching for icons and displaying them are different
things.
--
Marcos Caceres
http://datadriven.com.au
me.
If you want to save me some time, you could start listing all the
places where further clarification is needed and feel free to
recommend some text to add to make things better.
Kind regards,
Marcos
--
Marcos Caceres
http://datadriven.com.au
for both .htm and .html
files?
That is correct. Is that not clear enough? If no, can you suggest some
text that would make that more clear?
--
Marcos Caceres
http://datadriven.com.au
Regretively, I did not get time to draw up the list of todo's today
for PC. I will have it ready for the teleconf and can provide a quick
summary during the call. Good news is that well over half the feedback
has been responded to and the DoC is mostly up-to-date.
Marcos
On Wednesday, July 1
701 - 800 of 1132 matches
Mail list logo
