Change Details

* Have a simple node js script ready to send OP_RETURN messages * npm start * Send a normal tx from address A to address B with no message to ensure no regression on XEC sending function * Send outbound OP_RETURN tx from address A to address B with normal message string * Send outbound OP_RETURN tx from address B to address A with normal message string * verify both inbound and outbound OP_RETURN messages are displayed in the Transaction History tab for both wallets and not for other non-message txs * Send outbound OP_RETURN tx from address A to address B with empty string (bunch of spaces) message. Once D10363 lands, this message will not displayed in Cashtab as empty string messages are ignored in D10363's useBCH.js sendBCH() function. It will be displayed if you're reviewing this diff independently. * Send outbound OP_RETURN tx from address A to address B with a message containing over 150 characters (D10363 limits to 150 chars and below) and verify this is displayed appropriately by being cut off at appropriate height and width limits. This is to guard against mischievious users purposely spamming insanely long messages via nodejs to distort other users' tx history screen * Send outbound OP_RETURN tx from address A to address B with a message containing an extra long word and verify the long word is broken into multiple lines and height clipping CSS applied if necessary * Send outbound token tx and ensure the new OP_RETURN parsing logic in useBCH.js does not break existing eToken parsing logic * verify cross-browser compatibility in Firefox * npm run extension * verify OP_RETURN messages are displayed in extension mode

* Have a simple node js script ready to send OP_RETURN messages * npm start * Send a normal tx from address A to address B with no message to ensure no regression on XEC sending function * Send outbound OP_RETURN tx from address A to address B with normal message string * Send outbound OP_RETURN tx from address B to address A with normal message string * verify both inbound and outbound OP_RETURN messages are displayed in the Transaction History tab for both wallets and not for other non-message txs * Send outbound OP_RETURN tx from address A to address B with empty string (bunch of spaces) message. Once D10486 lands, this message will not displayed in Cashtab as empty string messages are ignored in D10486's useBCH.js sendBCH() function. It will be displayed if you're reviewing this diff independently. * Send outbound OP_RETURN tx from address A to address B with a message containing over 150 characters (D10486 limits to 150 chars and below) and verify this is displayed appropriately by being cut off at appropriate height and width limits. This is to guard against mischievious users purposely spamming insanely long messages via nodejs to distort other users' tx history screen * Send outbound OP_RETURN tx from address A to address B with a message containing an extra long word and verify the long word is broken into multiple lines and height clipping CSS applied if necessary * Send outbound token tx and ensure the new OP_RETURN parsing logic in useBCH.js does not break existing eToken parsing logic * verify cross-browser compatibility in Firefox * npm run extension * verify OP_RETURN messages are displayed in extension mode

* Have a simple node js script ready to send OP_RETURN messages * npm start * Send a normal tx from address A to address B with no message to ensure no regression on XEC sending function * Send outbound OP_RETURN tx from address A to address B with normal message string * Send outbound OP_RETURN tx from address B to address A with normal message string * verify both inbound and outbound OP_RETURN messages are displayed in the Transaction History tab for both wallets and not for other non-message txs * Send outbound OP_RETURN tx from address A to address B with empty string (bunch of spaces) message. Once D10363486 lands, this message will not displayed in Cashtab as empty string messages are ignored in D10363D10486's useBCH.js sendBCH() function. It will be displayed if you're reviewing this diff independently. * Send outbound OP_RETURN tx from address A to address B with a message containing over 150 characters (D10363D10486 limits to 150 chars and below) and verify this is displayed appropriately by being cut off at appropriate height and width limits. This is to guard against mischievious users purposely spamming insanely long messages via nodejs to distort other users' tx history screen * Send outbound OP_RETURN tx from address A to address B with a message containing an extra long word and verify the long word is broken into multiple lines and height clipping CSS applied if necessary * Send outbound token tx and ensure the new OP_RETURN parsing logic in useBCH.js does not break existing eToken parsing logic * verify cross-browser compatibility in Firefox * npm run extension * verify OP_RETURN messages are displayed in extension mode