public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 2/3] ui: tags: prevent pasting non plain-text content
Date: Tue, 24 Oct 2023 12:51:39 +0200	[thread overview]
Message-ID: <8185c74e-d3a3-4c6b-bdfa-e4446b9aa949@proxmox.com> (raw)
In-Reply-To: <5db9a4ea-fa58-4ecc-afff-f808a29b3b87@proxmox.com>

On 10/24/23 12:07, Thomas Lamprecht wrote:
> Am 24/10/2023 um 11:57 schrieb Dominik Csapak:
>> On 10/24/23 11:53, Thomas Lamprecht wrote:
>>> Am 19/10/2023 um 15:59 schrieb Dominik Csapak:
>>>> sry disregard this patch only, that property value is not supported in firefox :(
>>>>
>>>
>>> We could set it only to "plaintext-only" for non-firefox then though?
>>
>> sure not a problem, i just generally try to avoid browser specific stuff
>>
>> if there is a way to prevent pasting html in a sane way for all browsers
>> i'd prefer that, but did not have the time to look into that..
>>
> 
> OK, let's make "no special cases for browsers" a rule that should have as
> few as possible exceptions, that can only benefit users and devs reproducing
> issues.

that makes sense, i'll add a section to the javascript style guide, is that
fine with you?

> 
> I subscribed to the enhancement request [0] at Mozilla's Bugzilla, where
> they state that it's only blocked on the spec being to vague and lacking test
> cases, so once it's done and released in an ESR we can switch to this
> unconditionally
> 
> [0]: https://bugzilla.mozilla.org/show_bug.cgi?id=1291467#c22

i'll subscribe too, thanks for researching that




  reply	other threads:[~2023-10-24 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 13:36 [pve-devel] [PATCH manager 1/3] ui: tags: fix focus for edit mode Dominik Csapak
2023-10-19 13:36 ` [pve-devel] [PATCH manager 2/3] ui: tags: prevent pasting non plain-text content Dominik Csapak
2023-10-19 13:59   ` Dominik Csapak
2023-10-24  9:53     ` Thomas Lamprecht
2023-10-24  9:57       ` Dominik Csapak
2023-10-24 10:07         ` Thomas Lamprecht
2023-10-24 10:51           ` Dominik Csapak [this message]
2023-10-24 10:52             ` Thomas Lamprecht
2023-10-19 13:36 ` [pve-devel] [PATCH manager 3/3] ui: wizards: allow adding tags in the qemu/lxc create wizard Dominik Csapak
2023-10-24 14:48   ` Thomas Lamprecht
2023-10-24 14:49 ` [pve-devel] applied: [PATCH manager 1/3] ui: tags: fix focus for edit mode Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8185c74e-d3a3-4c6b-bdfa-e4446b9aa949@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal