Further expand the consent info storage limit to 1200

[zhouyx]

Closes #28668
An example stored value is

{"amp-consent:example-key":{"s":1,"r":"example-consent-string","m":{"cst":1,"ac":"example-additional-consent"}}}

[micajuine-ho]

Thanks for these changes from enforcing string size to whole storage size! Do you think realistically there are any pages that will be over the limit with their current storage size?

[micajuine-ho]

I'm curious, why dict, instead of object?

[zhouyx]

It doesn't make much of a difference here given that value is calculated internally.
But dict() returned value makes sure that JSON.Stringify() won't error out due to functions or any unparsed stuff in Object.

I used dict() also because that how we store values to localStorage. Kinda want to keep it the same.

amphtml/src/service/storage-impl.js

Lines 248 to 251 in 0a0269a

	this.values_[name] = dict({
	'v': value,
	't': Date.now(),
	});

[micajuine-ho]

Thanks for the explanation!

[olivervw]

Sorry to report this, but we are currently experiencing a '[CONSENT-STATE-MANAGER] Cannot store consent information which length exceeds 1200. Previous stored consentInfo will be cleared' error with our cmp solution on AMP. Are there any plans to extend the localStorage usage for amp-consent to allow more than 1200 characters (1600 b64 encoded) in a near future ?

[micajuine-ho]

Hi @olivervw , please see this comment regarding consent information size.