Navigation problems with binomial notation represented using <mmultiscripts>
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 68/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- rust, yaml
- Área
- accessibility
Línea de trabajo
Reproduce the MathML example in NVDA with MathCAT 0.7.6-rc.3, then read the relevant into-or-out-of-mmultiscripts rules in navigate.yaml and the rules that skip none and mprescripts. Done means Enhanced/Simple navigation announces semantic parts rather than literal base/subscript roles, while Character mode avoids the redundant subscript transition.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Navigation of a binomial coefficient represented using <mmultiscripts> produces unexpected structural labels in all three navigation modes.
MathML
<math id="0" display="block" xmlns="http://www.w3.org/1998/Math/MathML">
<mmultiscripts id="1">
<mi id="2">C</mi>
<mi id="3">m</mi>
<none id="4"/>
<mprescripts id="5"/>
<mi id="6">n</mi>
<none id="7"/>
</mmultiscripts>
</math>
This represents a binomial coefficient with presubscript n and postsubscript m.
Settings
- Language: English
- Speech style: SimpleSpeak
- Speech verbosity: Medium
- Overview: False
- Navigation verbosity: Verbose
- Auto zoom out: True
Tested through NVDA with MathCAT 0.7.6-rc.3 installed as an addon.
Observed behaviour
Enhanced and Simple (identical)
-
ZoomIn- land on
id="6" - hear:
"zoom in; in base; n"
- land on
-
MoveNext- land on
id="3" - hear:
"move right; in subscript; m"
- land on
The landing order n → m appears correct for the inferred binomial semantics, but the structural labels do not.
MathCAT's binomial-mmultiscripts inference converts this expression into a semantic binomial whose children are n and m. Therefore n is no longer the literal base of the original <mmultiscripts>, and m is no longer being navigated as its literal postsubscript.
I would expect semantic navigation to describe these as arguments/parts of the binomial rather than as "base" and "subscript".
For example, with the current generic navigation behaviour for semantic structures, something approximately like:
-
ZoomIn- land on
id="6" - hear:
"zoom in; in part 1; n"
- land on
-
MoveNext- land on
id="3" - hear:
"move right; in part 2; m"
- land on
would seem more consistent.
Character
-
ZoomIn- land on
id="2" - hear:
"zoom in; in base; c"
- land on
-
MoveNext- land on
id="3" - hear:
"move right; in subscript; m"
- land on
-
MoveNext- land on
id="6" - hear:
"move right; out of subscript; in subscript; in pre-subscript; n"
- land on
Character mode correctly follows the literal MathML structure and lands on the expected nodes.
However, the third announcement appears to contain a redundant structural transition:
"out of subscript; in subscript; in pre-subscript; n"
When moving from the postsubscript m across <none> and <mprescripts> to the presubscript n, I would expect something more like:
"move right; out of subscript; in pre-subscript; n"
or another equivalent transition that does not temporarily announce "in subscript" again.
Possible causes
There appear to be two potentially relevant areas in navigate.yaml.
For Enhanced/Simple, the inferred binomial still originates from <mmultiscripts>. The into-or-out-of-mmultiscripts navigation rule applies when:
@data-from-mathml='mmultiscripts'
and assigns roles according to literal child positions (base, subscript, superscript, etc.).
This may cause the two children of the inferred semantic binomial(n, m) to be incorrectly labelled as though they were still the first two children of the original <mmultiscripts>.
For Character mode, the rules that skip <none> and <mprescripts> perform additional Move2D/MoveNextZoom operations while moving to the following real script. This may be responsible for the extra "in subscript" announcement while crossing from the postscript to the prescript.
Disclosure: I asked ChatGPT for help to dig into the cause of this, so these guesses might well be wrong.
- Lenguaje dominante
- Rust
- Estrellas
- 130
- Forks
- 96
- Merge medio
- 1 d 1 h
- PR fusionados (30 d)
- 84
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de daisy/MathCAT
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
daisy/MathCAT#946 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
discussion
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Review French navigation fileAbiertodiscussion translation
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
daisy/MathCAT#675 · 4 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de daisy/MathCAT
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
swc-project/swc-ai-issues#164 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
pop-os/cosmic-player#367 ·
-
good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
servo/rust-smallvec#873 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
messense/dav-server-rs#82 ·
Los mantenedores suelen responder en 1 día