Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Voice input fails in browser address bars due to incorrect password field detection (v4.2.9, follow-up to #516)

Aberta Para iniciantes
  • Algo errado?
#713 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
76/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
android, kotlin
Domínio
backend, mobile

Direção de pesquisa

Leia VoiceInputManager.kt na parte de isBlockedEditor() e compare as verificações de senha com os utilitários que consideram a classe em InputTypeUtils.kt. Confira os testes existentes de entrada por voz, se houver, e verifique que os campos de URL da barra de endereço não sejam mais rejeitados, enquanto os campos de senha continuem bloqueados. O trabalho estará concluído quando a entrada por voz iniciar nas barras de endereço do navegador e continuar recusando campos de senha.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug

Describe the bug

Voice dictation still fails in browser address bars after the fix for #516, included in LeanType v4.2.9.

Tested browsers: Firefox, Chrome, and Brave. The issue occurs in all three.

The microphone button appears in the address bar, but tapping it shows:

Voice input not available or permission missing

Voice dictation works correctly in ordinary text fields, including input fields within webpages.

Relationship to #516

Issue #516 was closed as completed via commit 3373e94.

That commit removed this condition from InputAttributes.kt:

- hasNoMicrophoneKeyOption() ||

This stops the app's NO_MICROPHONE flag from hiding the microphone button in browser address bars. However, it addresses button visibility, not the separate activation-time check. The button is now visible but voice recording still fails.

Root cause identified in source code

LeanType uses two inconsistent password-field checks.

1. Microphone visibility — class-aware

InputTypeUtils.isPasswordInputType() checks both the input class and variation:

val maskedInputType = inputType and
    (InputType.TYPE_MASK_CLASS or InputType.TYPE_MASK_VARIATION)

Source: InputTypeUtils.kt, lines 56–65

2. Microphone activation — checks variation only

VoiceInputManager.isBlockedEditor() uses:

val variation = info.inputType and InputType.TYPE_MASK_VARIATION

return variation == InputType.TYPE_TEXT_VARIATION_PASSWORD ||
        variation == InputType.TYPE_TEXT_VARIATION_WEB_PASSWORD ||
        variation == InputType.TYPE_TEXT_VARIATION_VISIBLE_PASSWORD ||
        variation == InputType.TYPE_NUMBER_VARIATION_PASSWORD

Source: VoiceInputManager.kt, lines 1071–1079

Android assigns the same numeric variation (0x10) to these two types:

  • TYPE_TEXT_VARIATION_URI — URL fields (text class)
  • TYPE_NUMBER_VARIATION_PASSWORD — numeric password fields (number class)

Because isBlockedEditor() ignores TYPE_MASK_CLASS, a URL field can be incorrectly identified as a numeric password field. This explains the discrepancy between button visibility and activation.

Log evidence

The LeanType diagnostic log repeatedly shows the following immediately after tapping the microphone:

SuggestionStripView: click toolbar key VOICE
VoiceInputManager: canStartVoice: Blocked editor (password)

Other regular text fields successfully initiate recording and transcription. The logs establish that the password-field rejection is occurring; the source code indicates the cause of the misclassification.

To Reproduce

  1. Install LeanType v4.2.9 (standard flavor).
  2. Open Firefox, Chrome, or Brave.
  3. Focus the browser address bar.
  4. Tap LeanType's visible microphone button.

Actual behavior: Recording does not start. Instead, the keyboard reports Voice input not available or permission missing.

Expected behavior

Voice dictation should activate in browser address bars and insert recognized text as it does in regular text fields.

Suggested fix

Make VoiceInputManager.isBlockedEditor() check both input class and variation, ideally by reusing the existing class-aware utilities:

fun isBlockedEditor(info: EditorInfo?): Boolean {
    if (info == null) return false

    return InputTypeUtils.isPasswordInputType(info.inputType) ||
           InputTypeUtils.isVisiblePasswordInputType(info.inputType)
}

This avoids duplicating password-detection logic and prevents collisions between URL fields and numeric password fields.

Screenshots

A screenshot showing the error message in the address bar is available. LeanType diagnostic logs are also available, showing repeated Blocked editor (password) warnings.

App version & Flavor

  • Version: 4.2.9 (4209)
  • Flavor: Standard
  • Voice provider: Online

Device Info

  • Model: Nothing Phone (2)
  • OS version: Android 16 (SDK 36)

Related: #516 — Voice dictation does not work in browser URL bars. Its fix addressed microphone-button visibility, but the separate activation-time password-field detection remains defective. Please track this as a follow-up to #516.

Linguagem predominante
Kotlin
Estrelas
1k
Forks
59
Merge médio
13h 11min
PRs com merge (30d)
47

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de LeanBitLab/LeanType

Todas as issues de LeanBitLab/LeanType

Issues semelhantes

Mais issues de Kotlin

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.