Add unpublished Safari build

[fregante]

Related to #14

This PR currently doesn't include any custom code, it's just the direct result of:

xcrun safari-web-extension-converter distribution/ --project-location safari --app-name 'Refined GitHub' --bundle-identifier 'com.sindresorhus.refinedGitHub'

Next:

• Find solution the lack of negative lookbehinds support 🤦‍♂️

  

  I saw that @lautis’ wrapper forces compatible versions of those modules for Safari:

  lautis/refined-github-safari@8eebe28#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519L10

  We can just undo Update dependencies; make Firefox 78 the minimum version #3316

• Cleanup options CSS

• Fix options’s filter and fit-textarea

• Find out why permission hosts aren't automatically allowed

[sindresorhus]

You need to gitignore:

xcuserdata
project.xcworkspace

[fregante]

You need to gitignore:

That's what I was hoping to find out with this PR 🎉

---

Also, initial Safari compatibility achieved

Options are preserved too:

[fregante]

Firefox vs Safari vs Chrome

[fregante]

How to test

1. Install XCode 12 and Safari 14

2. You probably need to enable Allow Unsigned Extensions in Safari’s Develop menu.

3. Run:

   npm run build
   npm run pack:safari
   npm run start:safari

4. I also had to click Edit websites under Safari Preferences -> Extensions -> Refined GitHub and manually allow GitHub.com.

Questions

4. About the number 4 above: Is this because it's unsigned? Does it happen for you as well? How can we avoid this?

Review

All the new files are autogenerated. Suggestions welcome, even if it's just to rename files.

Next

I think this PR won't need substantial work, but the next steps in new PRs will be:

• @sindresorhus sign the extension (?)
• @sindresorhus do you want to publish an initial version manually?
• Set up Fastlane
• Improve icons
• Meta: Find out if there's a way to auto-pack the extension while developing
• Enterprise: Look into Enterprise support

[fregante]

Regarding point 4: I think there's no way around it. permissions is essentially ignored and always acts as optional_permissions, the user has to enable the extension. More information from ~10:00 to ~15:00 in the video: https://developer.apple.com/videos/play/wwdc2020/10665/

Enterprise support in Safari requires some changes:

• Safari offers a UI to enable the extension on any domain, so webext-domain-permission-toggle needs to be dropped
• webext-dynamic-content-scripts doesn't seem to work, but I think this can be replaced by <all_urls> under content_scripts. This is perfect, but it requires a custom manifest.json for Safari
• The domain picker currently appears for everyone, so it needs to be hidden in Safari. The cause appears to be Safari support: every host permission is reported as "additional" fregante/webext-permissions#1

[lautis]

You already use the nolookbehind variants, so that's fixed 👍

Another patch I have for Safari is the following CSS:

.rgh-parse-backticks {
  display: inline-block;
}

This fixes line-wrapping of code blocks in issues list.

[fregante]

Another patch I have for Safari is the following CSS:

Thanks for making me notice that. It looks like a Safari bug. inline-block will prevent wrapping though, but it looks like moving the sr-only elements outside rgh-parse-backticks fixes it:

https://github.com/sindresorhus/refined-github/blob/a38244e63e108b141745a80f0264ebd1ff6740b0/source/github-helpers/parse-backticks.tsx#L11-L15

<span className="sr-only">`</span> 
<code className="rgh-parse-backticks">{text.trim()}</code> 
<span className="sr-only">`</span>