summaryrefslogtreecommitdiffhomepage
path: root/desktop/packages/mullvad-vpn/src/renderer
AgeCommit message (Collapse)AuthorFilesLines
2025-11-04Refactor remaining components to use new SwitchOliver7-100/+35
2025-11-04Remove Animate componentOliver16-357/+0
2025-11-04Replace Animate with AnimatePresence in Accordion componentOliver1-10/+25
2025-10-31Add robber languageOskar1-0/+4
2025-10-30Convert tag transformers from Components to render props patternTobias Järvelöv1-6/+8
This isn't necessarily better, but with our Mocha test setup we did not see the expected result in our tests when a React component was passed to the formatHtml function, likely due to something missing when JSX is transformed.
2025-10-30Allow to pass in custom components to formatHtmlTobias Järvelöv1-31/+27
2025-10-29Use outline for text field input state stylingOliver1-38/+39
2025-10-27Rewrite formatHtml to fix bugs in previous implementationTobias Järvelöv1-17/+34
When the functionality to format `em` tags was added a buggy behavior was introduced. This buggy behavior stems from the logic to match the input string against the tags we want to format, namely <b> and <em>. We mistakenly operate against the original string at all times when we match each tag, which means that for a string which contains '<b>something</b>' the content is correctly identified by the <b> tag's test function and gets rendered with the appropriate React component. However, since the original string is used for every tag this means the same string will also be handled by the next tag. In this case the <em> tag's test function will evaluate the string, '<b>something</b>' and see that it does not match and herein lies the buggy behavior. When a tag's test function does not get a match for the string it will render it as a fragment and push it to the formatted string array. This means that we get duplicated entries in the formatted string array because we get both the React component version of the string and the fragment version of the string. This buggy behavior is now fixed by passing the result of the first tag operations to the next tag. This ensures that once a part of the original string has been matched and turned into a component it can not be matched again by another tag.
2025-10-23Disable UpgradeButton when no upgrade existsTobias Järvelöv1-1/+4
2025-10-23Add show variable for conditional render to adhere to the style guideTobias Järvelöv1-1/+3
2025-10-23Make upgrade details conditionally render based on if an upgrade existsTobias Järvelöv2-50/+52
Render NoUpdateAvailable if the app upgrade does not exist
2025-10-23Add NoUpgradeAvailable componentTobias Järvelöv3-0/+50
2025-10-23Add AppUpgradeHeader componentTobias Järvelöv3-0/+15
2025-10-23Add hook useHasUpgradeTobias Järvelöv2-0/+10
2025-10-23Sort exports alphabeticallyTobias Järvelöv1-1/+1
2025-10-23Fix typo in translators noteTobias Järvelöv1-2/+2
2025-10-23Remove irrelevant TODOTobias Järvelöv1-1/+1
This usage pattern became the standard after all.
2025-10-20Use motion for in-app notification transitionTobias Järvelöv2-51/+44
2025-10-17Replace use of img element with Image componentTobias Järvelöv2-7/+15
2025-10-17Use LWO from strings constant in SelectLocationTobias Järvelöv1-1/+1
2025-10-17Fix missing key for fragmentTobias Järvelöv1-1/+1
2025-10-17Remove use of PATH_PREFIXTobias Järvelöv5-23/+6
2025-10-15Use Listbox component for selecting languageOliver1-16/+20
2025-10-15Rename SelectLanguage to SelectLanguageViewOliver2-3/+3
2025-10-15Move select language to views folderOliver4-15/+17
2025-10-15Rename UserInterfaceSettings to UserInterfaceSettingsViewOliver3-4/+8
2025-10-15Rename LanguageButton to LanguageListItemOliver5-5/+5
2025-10-15Use SettingsToggleListItem component in user interface settingsOliver5-117/+62
2025-10-15Move user interface settings components to separate foldersOliver14-179/+224
2025-10-15Move user interface settings to views folderOliver4-17/+25
2025-10-15Use new Switch component in BetaListItemOliver1-41/+26
2025-10-13Remove translation strings for LWO and QUICTobias Järvelöv2-3/+4
Instead use the value in the strings constant directly.
2025-10-10Use same error message when fetching devices failsOliver2-8/+3
2025-10-10Handle errors and retries in manage devices viewOliver12-73/+174
2025-10-10Add useQuery hookOliver2-0/+59
2025-10-10Add EmptyState componentOliver14-0/+138
2025-10-10Add align self prop to Flex componentOliver1-0/+3
2025-10-10Update Button width to use full width in more layoutsOliver1-13/+13
2025-10-10Use css helper in Text componentOliver1-1/+1
2025-10-10Add and pass devices property to DeviceListOliver6-24/+28
2025-10-10Add and use format device name hook and util functionOliver7-13/+16
2025-10-10Add and use format date hook in DeviceListItemOliver3-2/+9
2025-10-10Remove no-op catch blocks when fetching devicesOliver2-13/+7
2025-10-10Update text in remove device confirm dialogOliver1-5/+8
2025-10-10Refactor device list item remove button into separate componentOliver4-18/+32
2025-10-10Use AnimatedList component in device listOliver1-7/+8
2025-10-10Add AnimatedList componentOliver5-0/+56
2025-10-10Add MotionConfig to app rootOliver1-1/+4
2025-10-10Add em to allowed tags in verify translations scriptOliver1-1/+1
2025-10-10Add support for em tag in formatHtmlOliver1-8/+53
Copyright © 2025 - 2026 Wayne Cole. WTFPL. Attribution appreciated. No warranty. Not liable for bodily damages.