On Sun, Jun 18, 2017 at 3:58 PM, Carsten Haitzler <ras...@rasterman.com> wrote:
> On Sun, 18 Jun 2017 15:22:04 -0700 Cedric BAIL <cedric.b...@free.fr> said:
>> On Sun, Jun 18, 2017 at 3:07 PM, Andrew Williams <a...@andywilliams.me> 
>> wrote:
>> > Can we be a little careful with that response? The behaviour you think
>> > people are relying on is undocumented and confusing. Are people truly
>> > relying on the "HTML encoding" behaviour of user input?
>> > I think that something so unintuitive is better fixed rather than live with
>> > it forever!
>> > Simple user input such as "user<email>" is not being returned as expected
>> > and I really don't want to be the kind of framework that instructs
>> > developers to use workarounds especially as we roll out a shiny new API.
>>
>> I do agree with both of you, Kai and Andrew. My proposal to fix this
>> problem is to fix it in the new API, eo based, and make sure that we
>> don't repeat this problem. What do you think Daniel ?
>
> i disagree. we should do markup by default in most places where text is to be
> displayed. not only do the back-ends already do it (textblock) it's convenient
> for just adding some bold or underlined text but also allows us to trivially
> extend. add another method to get/set plain utf8. markup in general is more
> useful.

It is obviously confusing to people and has created bugs in the past.
People do expect they get text when they ask for text, not markup. If
you call .text() in JS, you don't get markup, you get text. I really
believe this is making our API harder to use without mistake.
.text.get() and .markup.get() should be 2 differents exposed API. Them
being available on every object is fine, but text should not return
markup.
-- 
Cedric BAIL

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to