On 2012/08/13 18:19, Masayuki Nakano wrote:
On 2012/08/13 17:32, Neil wrote:
Masayuki Nakano wrote:
On 2012/08/13 4:57, Neil wrote:
it seems as if you can't make the wheel scroll more slowly any more?
Currently, yes. The reason for not supporting slower scrolling isn't
technical reason
mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
--
Masayuki Nakano masay...@d-toybox.com
Manager
As*Event() methods return nullptr.
You should not use static_cast for Widget*Event and Internal*Event
anymore because it may cause wrong casting bug with some mistakes
(actually, there was such bug!).
I hope this change makes you happy!
--
Masayuki Nakano masay...@d-toybox.com
Manager
| for downcasts to
most-derived event types, and dynamic_cast for downcasts to
non-most-derived event types.
Masayuki Nakano:
Please use As*Event() in case #1 and #2. As you said, we can use
static_cast since there is eventStructType. However, it's NOT safe
because we *might* take mistakes. Actually
it as blocking bug 968056.
Of course, if you fix the new bugs filed for #2, it helps me very much.
But it's very helpful to me if you just file bugs for #2.
Thanks in advance.
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan
on cross-browser script.
If there is a problem, it must be like this:
if (navigator.userAgent.indexOf(Firefox) 0) {
// handling non-printable keys with keypress event handler
}
I cannot say there is no such web sites, however, I guess (and hope)
it's minority.
--
Masayuki Nakano masay...@d
mozilla::dom namespace for DOM event
classes, DOM prefix may be redundant. However, DOM prefix is clearer if
its users use using namespace mozilla::dom;.
Any ideas?
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan
Hi,
On 2014/02/12 23:22, Boris Zbarsky wrote:
On 2/12/14 4:46 AM, Masayuki Nakano wrote:
I'm not sure which is the best name for the classes. E.g., DOMWheelEvent
vs. PointerEvent.
I believe in this case PointerEvent is correct, because
http://www.w3.org/TR/pointerevents/#pointerevent
.
Thanks in advance.
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
'Touch.h',
42 ]
Now, they are exported as mozilla/dom/*.h.
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
because it's clear rule and non-nsDOM* classes use classes
which are defined in other modules (i.e., not in mozilla::dom namespace).
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev
in advance.
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Thank you for the reply, but sorry for the delay.
On 2014/06/20 23:25, Benjamin Smedberg wrote:
On 6/19/2014 10:00 PM, Masayuki Nakano wrote:
When I work on some bugs, I need to add a new option for a pref
switchable behavior, e.g., if we need to add a new option to a feature
and the new one
Hi, I wrote a draft of the guideline in MDN roughly.
I hope a lot of developers discuss the rules and improve this draft!
Thanks in advance.
On 2014/06/30 16:24, Masayuki Nakano wrote:
Thank you for the reply, but sorry for the delay.
On 2014/06/20 23:25, Benjamin Smedberg wrote:
On 6/19
On 2014/06/30 22:51, Masayuki Nakano wrote:
Hi, I wrote a draft of the guideline in MDN roughly.
I hope a lot of developers discuss the rules and improve this draft!
Oops, the draft is here. Sorry for the spam.
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Preferences
://bugzilla.mozilla.org/show_bug.cgi?id=1126673
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
://bugzilla.mozilla.org/show_bug.cgi?id=1134542
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
same style as our current style. IE doesn't have any special
style for them (i.e., rendered like simple span).
The bug to change the style:
https://bugzilla.mozilla.org/show_bug.cgi?id=1157083
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan
will be reported, we should
disable it before release.
The bug to turn on:
https://bugzilla.mozilla.org/show_bug.cgi?id=478029
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform
/html/DOM3-Events.html#h-event-modifier-initializers
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
, mochitest has them, though)
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
,
};
--
Masayuki Nakano masay...@d-toybox.com
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
outstanding code reviews by the end of this
month.
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
/base/nsITextInputProcessor.idl
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla
to support limited support of TSF on legacy Windows.
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
know. Smaug might be a
good reviewer for that.
Thanks in advance.
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listin
On 2016/04/12 20:27, Henri Sivonen wrote:
On Tue, Apr 12, 2016 at 7:45 AM, Masayuki Nakano <masay...@d-toybox.com> wrote:
So, my question is, why do we still have Qt widget in mozilla-central? What
the reason of keeping it in mozilla-central?
My understanding is that
of keeping it in mozilla-central?
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Done. Will be in 49.
On 2015/09/17 18:40, Masayuki Nakano wrote:
Summary: Drop TSF support only from WinXP and WinServer 2003.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1205600
Platforms: Windows XP, Windows Server 2003 and Windows Server 2003 R2
Estimated or target release: Gecko 44
iling list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.m
::WSRunObject::WSFragment
nsWSRunObject::WSPointmozilla::WSRunObject::WSPoint
nsEditor::CreateTxnForIMEText()
mozilla::EditorBase::CreateTxnForComposiiton()
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
_
needs to be read just once, store the value in some
static variable or so.
-Olli
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
--
Masayuki Nakano <masay...@d-toybox.com>
Software En
to add a rule to the coding style guide.
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
cgi?id=1312991
Note that I don't want to do them in 52 because 52 will be the next ESR.
So, I'd like to do them in 53.
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platfo
Hi,
I'm looking for some documents which explain when we need to touch
CLOBBER to avoid build failure. However, I've not found such document
yet. I see such information only in CLOBBER about WebIDL change.
So, is there any document which lists up when we need to touch CLOBBER?
--
Masayuki
#Dispatch_KeyboardEvent_across_BrowserElements
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1322736
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internationalization, Mozilla Japan.
___
dev-platform mailing list
dev-platform@lists.mozil
to stop supporting multiple selection only in
editor if the feature is not so loved by users.
I filed a bug for discussing this issue here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1323681
Feel free to comment anything.
Thanks in advance.
--
Masayuki Nakano <masay...@d-toybox.com>
M
On 2016/12/20 8:00, Mats Palmgren wrote:
On 12/15/2016 10:46 AM, Masayuki Nakano wrote:
> Supporting multiple selection in editor makes our editor code
> complicated.
Why is that so exactly? By necessity, the code already operates
on one Range, right? so why can't we implement som
ON_IME_CONVERTEDTEXT,
SELECTION_IME_SELECTEDCONVERTEDTEXT and SELECTION_FIND. So, perhaps, you
don't need to mind about such feature.
(Although, I don't know which selection type is used in location bar.)
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Internati
be changed/removed during handling other selection
ranges. We don't have any spec how do we behave in such case.
I think we should probably ask other browser vendors about this again so
that we can plan our future here better.
I agree.
--
Masayuki Nakano <masay...@d-toybox.com>
Manager, Inte
.
On Fri, Dec 16, 2016 at 12:16 AM, Masayuki Nakano <masay...@d-toybox.com>
wrote:
Hi,
I'm looking for some documents which explain when we need to touch CLOBBER
to avoid build failure. However, I've not found such document yet. I see
such information only in CLOBBER about WebIDL chang
On 2016/12/16 19:53, Mike Hommey wrote:
On Fri, Dec 16, 2016 at 05:16:25PM +0900, Masayuki Nakano wrote:
Hi,
I'm looking for some documents which explain when we need to touch CLOBBER
to avoid build failure. However, I've not found such document yet. I see
such information only in CLOBBER
.
The bug is bug 1347079:
https://bugzilla.mozilla.org/show_bug.cgi?id=1347079
Thanks in advance.
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozil
/show_bug.cgi?id=1347073
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ssion reports after
reaching risky patch to the release especially when it's limited to
non-English users.
So, in this case, I think we'd get regression reports of web apps which
is used in world wide. Otherwise, we wouldn't get regression reports
until releasing the n
isn't available.
Anyway, I believe that this makes 57 look nicer for Japanese users!
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=548311
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1354004
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1351332
[4] https://bugzilla.mozilla.org/show_bug.cgi
you need to
QI to nsIEditor first. So, if you need to add new scriptable method
which treat editor, using nsIEditor is better than other editor
interfaces since QI cost is not so cheap.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1060051
--
Masayuki Nakano <masay...@d-toybox.com>
So
by
EditorBase and HTMLInputElement.
https://searchfox.org/mozilla-central/rev/224cc663d54085994a4871ef464b7662e0721e83/dom/html/nsIPhonetic.idl
Nobody (including add-ons) uses them now. So, we can get rid of them.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1363278
--
Masayuki Nakano <ma
nsIEditorIMESupport is an empty interface. Members were moved to
nsIEditor and nsIEditorIMESupport was made a subclass of it.
This interface is now completely unused. So, it should be removed from
the tree completely.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1325281
--
Masayuki
I like using reference to argument if it's non-nullable.
In Core::Editor module, such arguments are already replaced with
reference in a lot of places.
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform m
easily in HTML. Perhaps, capsuling with Shadow DOM?
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
`mach try` with a specific set of test
directories. It will generate a set of --try-test-paths flags to
restrict tests to those paths, and only run the first chunk of any
group. Without that, groups shift around too much to be reliable.
On Fri, Sep 15, 2017 at 10:03:00AM +0900, Masayuki Nakano
ittent), often I end up running all the
mochitest-browser tests, looking at every log until I find the chunk
where the test is, and retrigger just that chunk. The chunk number
changes based on the platform and debug/opt, so it's painful.
Is there a way to trigger only the chunk that will contain a given
test
which path causes a bug.
If it's impossible, I'll create a tryserver build with each ancestor
caller logs the path, though.
Thanks in advance.
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing li
On 10/14/2017 12:29 AM, Masayuki Nakano wrote:
Ted, really sorry for the delay to say "Thank you" because of too busy
of my life.
I tried to do this on my environment (Ubuntu), then, I succeeded to get
a pretty stack trace even from trysever build.
1. Put |#include "
tryserver build from terminal.
7. Save stack trace to a text file.
8. Run |/tools/rb/fix_linux_stack.py < stack.txt|
Thank you very much!
On 9/22/2017 9:55 AM, Ted Mielczarek wrote:
On Thu, Sep 21, 2017, at 08:51 PM, Masayuki Nakano wrote:
I'd like to get pretty stack trance which shows meth
, ISHIKAWA,chiaki wrote:
Hi,
I use firefox under Windows most of the time, and so it will be very nice.
But obviously this is only for Windows platform, and
does not affect linux or OSX versions. Correct?
On 2017/08/23 14:19, Masayuki Nakano wrote:
Hi,
We decided that we should change our defaul
that this feature won't be exposed to attributes of "wheel" events.
This is just a default action change and same behavior as Chrome.
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing l
On 10/18/2017 4:08 PM, Jet Villegas wrote:
That is, do I owe you another steak? :-)
Always welcome another steak :-D
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozil
- Alt combination for
shortcut keys at least on Windows.
Note that if active keyboard layout does not have AltGr key,
getModifierState("AltGraph") always returns false (even if both Ctrl and
Alt are pressed).
The bug: https://bugzilla.mozilla.org/show_bug.cgi?id=90075
?id=968056
2: https://w3c.github.io/uievents/#legacy-keyboardevent-event-types
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
And currently, I'm working on making HTMLEditRules not derived from
nsIEditActionListener:
https://bugzilla.mozilla.org/show_bug.cgi?id=1430021
And nsIEditActionListener::Will*() will be removed because of no users:
https://bugzilla.mozilla.org/show_bug.cgi?id=1430319
--
Masayuki Nakano <ma
/EventUtils.js#835-905
*4 https://bugzilla.mozilla.org/show_bug.cgi?id=553149
*5 https://bugzilla.mozilla.org/show_bug.cgi?id=1433648
*6 https://bugzilla.mozilla.org/show_bug.cgi?id=1434317
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, M
:
document.execCommand("defaultParagraphSeparator", false, "br");
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
/docs/Web/Guide/HTML/Editable_content#Differences_in_markup_generation
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
org/show_bug.cgi?id=1452538#c19
On 2018/04/05 15:58, Masayuki Nakano wrote:
This incompatibility is pointed by W3C's Editing API WG:
https://github.com/w3c/editing/issues/171
Gecko has some specific editing UI of HTML editor.
1. Resiziers of , , absolute positioned elements.
2. Adding new table
;anchor" is
used in comm-central and BlueGriffon. Due to not defined as an Atom, it
does not make sense to keep supporting this value.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1484092
The first release of this change will be 63.
--
Masayuki Naka
On 4/7/2018 12:39 AM, Ehsan Akhgari wrote:
On Thu, Apr 5, 2018 at 11:08 PM Masayuki Nakano <masay...@d-toybox.com
<mailto:masay...@d-toybox.com>> wrote:
On 4/6/2018 2:50 AM, Ehsan Akhgari wrote:
> Hi Masayuki,
>
> First of all, thank you for taking on thi
.
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
sites written in
Japanese...
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
toolbars.
Then, you'll see grabber to move the black border box at top edge of the
box and you can move the box with dragging. That's one of the feature of
absolutely positioned editor available even on Firefox.
--
Masayuki Nakano <masay...@d-toybox.com&g
On 4/10/2018 4:40 PM, Brian Birtles wrote:
On Fri, Apr 6, 2018 at 10:26 AM, Masayuki Nakano <masay...@d-toybox.com>
wrote:
Does somebody know some lists of web sites which use vertical
writing-mode? Unfortunately, I don't know web sites which use writing-mode
heavily even though I usuall
:
https://bugzilla.mozilla.org/show_bug.cgi?id=1449564
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On 4/10/2018 5:53 PM, Karl Dubost wrote:
Masayuki,
Le 6 avr. 2018 à 17:26, Masayuki Nakano <masay...@d-toybox.com> a écrit :
Does somebody know some lists of web sites which use vertical writing-mode?
Kobo Taiwan for example has preview of books in vertical writing mode.
see
ntally.
This is interesting case. This is not what we're looking for, but this
is a case of web developers trying to fix the issue by themselves. I.e.,
they must be thinking that horizontal scroll isn't useful even if the
block direction is completely horizontal.
--
Masayuki Nakano <masay...@d-t
On 4/11/2018 4:34 PM, Karl Dubost wrote:
Le 11 avr. 2018 à 15:14, Masayuki Nakano <masay...@d-toybox.com> a écrit :
However, oddly, I cannot show the preview on Firefox nor Nightly. When I click the
"preview", the website says "saved the preview" but I cannot ac
to nsIEditor.transactionManager.numberOfUntoItems and
nsIEditor.transactionManager.numberOfRedoItems.
So, we don't need to keep maintaining these shortcut methods anymore.
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
___
dev-pl
by anybody (it seems that it was used by ChatZilla, but according to its
website, it's not active) and this causes a lot of unnecessary virtual
calls and QI at D and Paste in editor. So, I don't think that we
should keep this feature anymore.
--
Masayuki Nakano <masay...@d-toybox.com>
So
ot; event is the right event because "keydown"
event and "keyup" event may not be fired even after the bug fix. For
example, if the IME is backend of voice input or handwriting system,
Gecko won't fire "keydown" nor "keyup" event unless OS or IME
synt
couldn't fix new
oranges with this approach. So, it works with some condition, but I
don't know about this.
So, I'll keep struggling with regressions of this behavior change.
However, probably, we won't get regression reports for minor UI, e.g.,
running only first time to use somethin
about key operation in some web apps, please
file a bug for each web app, and block bug 1479964.
1: https://bugzilla.mozilla.org/show_bug.cgi?id=218415
2: https://bugzilla.mozilla.org/show_bug.cgi?id=1479964
3: https://bugzilla.mozilla.org/show_bug.cgi?id=1497546
4: https://bugzilla.mozilla.org
We've decided to put this off at least 66.
https://bugzilla.mozilla.org/show_bug.cgi?id=1520756
On 2018/11/30 10:37, Masayuki Nakano wrote:
Summary: We'll set keyCode of "keypress" event to its charCode value if
keyCode is 0, charCode of "keypress" event to its keyCode val
, the
fix broke another internet app (bug 1514940).
Therefore, we put off to reship this at least until 66.
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev
We've decided to put this off at least 66.
https://bugzilla.mozilla.org/show_bug.cgi?id=1520756
On 2018/11/30 10:47, Masayuki Nakano wrote:
Summary: Enable window.event which can access dispatching event from
everywhere.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=218415
Link
to Level 2 support
with pref, "dom_input_events.conform_to_level_1", although could be
changed in review process).
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
isable
this new behavior only in specific domains. If we'll get broken web
apps even after release, we and users can disable it with using this
blacklist.
Enabling patch has been landed from:
https://bugzilla.mozilla.org/show_bug.cgi?id=1496288
because we need to manage those changes as a set.
hanges which will be mentioned in
following posts.
Enabling patch has been landed from:
https://bugzilla.mozilla.org/show_bug.cgi?id=1496288
because we need to manage those changes as a set.
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-plat
id=1496288
because we need to manage those changes as a set.
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
um/#!topic/mozilla.dev.platform/E8DyIJBhu1g
https://groups.google.com/forum/#!topic/mozilla.dev.platform/IWLLJmoGroA
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
nt of text input
from keyboard directly (i.e., not via IME). "input" and "beforeinput"
are similar to "keypress", but they are fired only when an editor has
focus and with any input devices/middle wares.
Currently, I'm working on implementing "beforeinput". It a
On 2018/11/30 20:42, James Graham wrote:
On 30/11/2018 01:37, Masayuki Nakano wrote:
web-platform-tests: N/A due to requiring user input, but we have
mochitests with synthesized events.
I think it should be possible to write web-platform-tests for this kind
of thing now, using the testdriver
te that this event is listened by only 0.0003% inner-windows for now
(currently, we collect the data only from Nightly testers).
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
the result. I'll keep changing other GetPresShell() methods
too when I have time, but of course, you're welcome if you do that
instead of me ;-)
Regards,
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform
/PresShell.cpp#7190-7586
3.
https://searchfox.org/mozilla-central/rev/8ff2cd0a27e3764d9540abdc5a66b2fb1e4e9644/layout/base/PresShell.h#499-1261
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https
- brennie
On Wed, Feb 6, 2019 at 7:27 PM Masayuki Nakano wrote:
I sometimes rewrite patches from new contributor and commit them with
`-u` and the contributors name and email address, and land the patches
for them. E.g., https://bugzil.la/1513405
Is it possible to do that via Phabricator
bugs for them.
Currently, I plan to enable them by default in all channels like
InputEvent.inputType. If we would get web-compat issues, e.g., they are
used to detect "beforeinput" event support, then, I'd disable them in a
follow up bug.
--
Masayuki Nakano
Software Engineer, Mozilla
been set as blocker bugs to https://bugzil.la/1514775.
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
--
Masayuki Nakano
Working on DOM, Events, editor and IME handling at Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
detection.
--
Masayuki Nakano
Working on DOM, Events, editor and IME handling at Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
not devirtualize the methods of them newly,
they perhaps have already been done by compiler.
--
Masayuki Nakano
Working on DOM, Events, editor and IME handling at Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org
1 - 100 of 114 matches
Mail list logo