Section 3.1.2 of the Lightning paper (Version 0.5.9.2, last modified 14 January 2016) discusses ways to fix the transaction malleability issue, which prevented Bitcoin transactions from spending UTXO from yet unconfirmed transactions. Specifically, it mentioned
SIGHASH_NOINPUT transaction type.
As far as I know, the malleability issue was fixed with the Segwit soft fork in August 2017. Was the malleability issue fixed with
SIGHASH_NOINPUT or with some other method? How does it affect the Lightning network design as described in the paper?