Github messages for voidlinux
 help / color / mirror / Atom feed
From: jnbr <jnbr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Firefox password fields and file URLs broken by multiprocess setting
Date: Tue, 21 Apr 2020 22:36:38 +0200	[thread overview]
Message-ID: <20200421203638._5IJYeKmaClLD695GO2qUQ8iSh8Vw3KjWEJfzu1vbSA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12885@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

Closed issue by svenper on void-packages repository

https://github.com/void-linux/void-packages/issues/12885

Description:
### System

* xuname:  
  `Void 5.2.4_1 x86_64-musl GenuineIntel notuptodate hold rrnFFFFFFFFF`
* package:  
  firefox-68.0.1_1
  firefox-esr-60.8.0_1

### Expected behavior

1. Selecting password input fields do not crash the tab.
2. `file://` URLs do not crash.

### Actual behavior

When `browser.tabs.remote.autostart` is set to `true` (the default) :
1. Selecting password input fields crash the tab.
2. `file://` URLs crash.

### Steps to reproduce the behavior

```
rm -rf /tmp/firefox-void-debug
mkdir /tmp/firefox-void-debug
gdb --args /usr/bin/firefox --profile /tmp/firefox-void-debug --no-remote --new-instance --save-recordings --private-window 'https://bug1451466.bmoattachments.org/attachment.cgi?id=8965047' 2>&1 | tee /tmp/firefox.log
```

  parent reply	other threads:[~2020-04-21 20:36 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07 14:18 [ISSUE] Firefox password fields broken by IBus voidlinux-github
2019-07-18  2:15 ` Firefox password fields broken voidlinux-github
2019-07-19 22:41 ` Firefox password fields and file URLs broken by multiprocess setting voidlinux-github
2019-07-19 23:38 ` voidlinux-github
2019-07-20  0:01 ` voidlinux-github
2019-07-20  0:03 ` voidlinux-github
2019-07-20  0:06 ` voidlinux-github
2019-07-20  0:06 ` voidlinux-github
2019-07-20  0:08 ` voidlinux-github
2019-07-20  0:31 ` voidlinux-github
2019-07-20  0:33 ` voidlinux-github
2019-07-20  0:36 ` voidlinux-github
2019-07-20  0:37 ` voidlinux-github
2019-07-20  0:45 ` voidlinux-github
2019-07-20 10:12 ` voidlinux-github
2019-07-20 13:51 ` voidlinux-github
2019-07-20 13:52 ` voidlinux-github
2019-07-20 15:59 ` voidlinux-github
2019-07-20 16:43 ` voidlinux-github
2019-07-20 17:28 ` voidlinux-github
2019-07-20 17:28 ` voidlinux-github
2019-07-21 22:40 ` voidlinux-github
2019-07-21 23:36 ` voidlinux-github
2019-07-22  0:16 ` voidlinux-github
2019-07-22  0:36 ` voidlinux-github
2019-07-23  9:16 ` voidlinux-github
2019-07-25 18:27 ` voidlinux-github
2019-07-30 13:29 ` voidlinux-github
2019-07-30 13:43 ` voidlinux-github
2019-07-30 13:59 ` voidlinux-github
2019-09-20 22:03 ` voidlinux-github
2019-09-28  2:28 ` voidlinux-github
2019-10-21  2:09 ` voidlinux-github
2020-01-12 18:30 ` voidlinux-github
2020-01-25 21:05 ` voidlinux-github
2020-04-12 20:10 ` zeliklil
2020-04-13  7:42 ` svenper
2020-04-21 20:36 ` jnbr [this message]
2020-04-21 20:36 ` jnbr
2020-04-21 20:56 ` svenper
2020-04-22  7:17 ` PureTryOut
2020-04-22  8:58 ` svenper
2020-04-22  9:56 ` PureTryOut
2020-04-22 10:49 ` svenper

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=20200421203638._5IJYeKmaClLD695GO2qUQ8iSh8Vw3KjWEJfzu1vbSA@z \
    --to=jnbr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).