https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
Scott Martin changed:
What|Removed |Added
CC||sc...@urbigenous.net
--- Comment #46 fr
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #45 from Elitre ---
I'll clarify that "it shouldn't happen" means just that it is not
useful/desirable to have it IMHO, or at least I can't think of a situation
where it would be.
--
You are receiving this mail because:
You are on
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #44 from Elitre ---
48891 and 53974 cover that specific problem. The wikimarkup warning is just a
warning, it does not stop you from doing anything.
As for this situation, of course it shouldn't happen. I can't recall
the b
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #43 from wikif...@gmail.com ---
What I mean is that you start with wikimarkup visible in the VE editing mode.
When you add something (''not'' wikimarkup) inside such wikimarkup, you get the
wikimarkup notice at the top right; but on
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #42 from Elitre ---
Hi there, I don't think I see your VEdit there. I did
https://www.mediawiki.org/w/index.php?title=User%3AElitre_%28WMF%29%2FSandboxVE&diff=794415&oldid=794413
and
https://en.wikipedia.org/w/index.php?title=User%3
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #41 from wikif...@gmail.com ---
Can someone explain why
[https://www.mediawiki.org/wiki/Communication?veaction=edit this page] seems to
accept wikitext markup, even in VE mode? On saving, it gives the "nowiki"
warning, but it doesn't
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #40 from Amalthea ---
(In reply to comment #39)
> [...] this bug is - by definition of the product - a WONTFIX.
James, this is simply not true. See comment #36 about auto formatting logic in
other visual word processors.
I really d
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
James Forrester changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
Chris McKenna changed:
What|Removed |Added
See Also||https://bugzilla.wikimedia.
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #38 from Chris McKenna ---
user John Broughton at en.wp comments:
"Rather than focus on improving [the warning about entering wikitext], a better
direction to go would be for VE to be able to convert wikitext to its
equivalent in VE
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #37 from kipod ---
(In reply to comment #22)
>
> If accidental insertion of wikitext is still an issue, we should focus on
> other
> ways to mitigate that issue.
2 things:
1) it's not an "if", and i do not think you guys should w
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
Amalthea changed:
What|Removed |Added
CC||Amalthea.wikimedia@googlema
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #35 from wikif...@gmail.com ---
Note that this question is included in the large
[[Wikipedia:VisualEditor/Default State RFC]] on the en.wikipedia, as question
5. The current tally, for what's it worth, is 28 supporting and 22 opposin
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
wikif...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #33 from kipod ---
(In reply to comment #31)
> I think that James' marking your bug as a duplicate was likely caused by his
> misunderstanding your request. He is part of the VE team but I have met him
> at Wikimeets a few times and
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #32 from MZMcBride ---
(In reply to comment #28)
Thank you for clarifying the two requests, Chris. That was super-helpful. :-)
(In reply to comment #29)
> maybe instead of coming here, what i should have done is to reopen and remov
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
Chris McKenna changed:
What|Removed |Added
See Also||https://bugzilla.wikimedia.
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #30 from kipod ---
oh, and what you describe as "the ideal solution", sounds a lot like bug 51899
to me.
peace.
--
You are receiving this mail because:
You are on the CC list for the bug.
_
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #29 from kipod ---
i think you are correct stating that these two "definitions" of the enhancement
request are not identical.
however, i came here to bug you guys with "my" definition of the request after
Forrester closed bug 51897
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #28 from Chris McKenna ---
There are at least two separate requests here. They are related in that they
both want to change the current behaviour of the two character sequence "[[" in
VisualEditor but they want to change it in incom
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #27 from kipod ---
i still do not think you understood the request.
it's not about transforming [[Foo]] to a link, it's about not getting [[Foo]]
into the page in the first place: as soon as the user types "[[", the "[["
should be
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #26 from MZMcBride ---
(In reply to comment #25)
> what we ask (at least, this is what i asked - see bug 51897, which was marked
> as duplicate of this one) is that when the user types "[[", VE will remove
> the "[[" from the page,
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #25 from kipod ---
i am not sure you understand the precise nature of this request, so let me
elaborate:
what we ask (at least, this is what i asked - see bug 51897, which was marked
as duplicate of this one) is that when the user
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #24 from MZMcBride ---
(In reply to comment #23)
> well, in all this products, when i misspell a word, the thing silently and
> valiantly just fix my mistake, instead of shouting at me[1].
> generally, this is known as "Auto correc
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #23 from kipod ---
please look above: in comment 15, Forrester did some namedropping: "Microsoft
Word, OpenOffice, Google Docs, Apple Pages and more".
well, in all this products, when i misspell a word, the thing silently and
valia
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #22 from Erik Moeller ---
We're listening, but in this case we're saying no, and that decision is final.
We can elaborate a bit more on the why if that helps, but parsing wikitext in
VisualEditor is absolutely not going to happen.
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #21 from kipod ---
(In reply to comment #17)
> So, let's calm down here.
>
> We're not "pissing on" anyone;
yes you are.
if you look at the different wikis, and if you search here with
"product=visualeditor" and "search word=nowi
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #20 from MZMcBride ---
Thank you very much for the clarification, Erik. I was just about to ask,
following comment 17, whether this was truly a wontfix (i.e., patches will not
be accepted) or whether it was simply a very low priorit
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #19 from Erik Moeller ---
"other user interfaces optimized for markup" -> "other user interfaces
optimized for completing actions quickly in VisualEditor that are fast to do in
markup"
--
You are receiving this mail because:
You a
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #18 from Erik Moeller ---
Sorry, but this is not something we'll ever do, as I explained in comment 9.
It's not simply a matter of prioritization - it's a matter of ensuring we can
provide a user experience that's not modeled on mar
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #17 from Oliver Keyes ---
So, let's calm down here.
We're not "pissing on" anyone; we're choosing to prioritise. Right now the devs
have got a lot of open bugs for the VisualEditor - things that actively /don't
work/. They've got a
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #16 from kipod ---
(In reply to comment #15)
> If you want an "accelerator key" for making links, use the standard one:
> Ctrl +
> K (or Cmd + K if you're on a Mac). This is the same shortcut as in Microsoft
> Word, OpenOffice, Goog
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
James Forrester changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
turi...@gmail.com changed:
What|Removed |Added
CC||turi...@gmail.com
--- Comment #14 f
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
kipod changed:
What|Removed |Added
Priority|Lowest |High
Status|RESOLVED
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
James Forrester changed:
What|Removed |Added
CC||fur.hew...@gmail.com
--- Comment #12
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #11 from ukexpat ---
WTG guys, piss off the user base even more with a WONTFIX on a no-brainer...
--
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
James Forrester changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
Erik Moeller changed:
What|Removed |Added
CC||e...@wikimedia.org
--- Comment #9 from
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #8 from James Forrester ---
(In reply to comment #7)
> (In reply to comment #6)
> > > (2) it requires the use of a mouse to add a link. :-(
> >
> > Not true, as discussed; I don't use the mouse to add links with VE (Ctrl+K
> > plus
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #7 from MZMcBride ---
(In reply to comment #6)
>> (2) it requires the use of a mouse to add a link. :-(
>
> Not true, as discussed; I don't use the mouse to add links with VE (Ctrl+K
> plus keyboard-based selection, as in other edi
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #6 from James Forrester ---
(In reply to comment #5)
> (In reply to comment #4)
> > I'm ambivalent about whether we would ever let this go live, given how
> > complicated it would make editing for people that don't know wikitext -
>
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #5 from MZMcBride ---
(In reply to comment #4)
> I'm ambivalent about whether we would ever let this go live, given how
> complicated it would make editing for people that don't know wikitext -
> consequently, marking as lowest prio
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
James Forrester changed:
What|Removed |Added
Priority|Unprioritized |Lowest
Status|NEW
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
Guillaume Paumier changed:
What|Removed |Added
CC||gpaum...@wikimedia.org
--- Comment
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
This, that and the other changed:
What|Removed |Added
See Also||https://bugzilla.wikimedia.
https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
This, that and the other changed:
What|Removed |Added
Summary|VisualEditor: convert |VisualEditor: automagically
47 matches
Mail list logo
