Update syntax hints in pref files to reflect the fact that you can't use computed values (e.g. 2 * 4)

RESOLVED FIXED in mozilla14

Status

()

Core
Preferences: Backend
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Justin Lebar (not reading bugmail), Assigned: Justin Lebar (not reading bugmail))

Tracking

unspecified
mozilla14
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
See bug 732820 comment 24 -- using computed values (e.g. 50 * 1024) in pref files causes major bustage.

We should update the "syntax hints" section at the top of the pref files to reflect this.
(Assignee)

Comment 1

5 years ago
Created attachment 605988 [details] [diff] [review]
Patch v1
Attachment #605988 - Flags: review?(dtownsend+bugmail)
(Assignee)

Updated

5 years ago
Assignee: nobody → justin.lebar+bug
I'd like to know *why* computed values don't work.  Is this not a vanilla JS file?
(In reply to Nicholas Nethercote [:njn] from comment #2)
> I'd like to know *why* computed values don't work.  Is this not a vanilla JS
> file?

The file is not executed as JS, it's just simply parsed as text
Attachment #605988 - Flags: review?(dtownsend+bugmail) → review+
> The file is not executed as JS, it's just simply parsed as text

Ah.  Maybe changing the suffix to .txt would help avoid confusion?
(In reply to Nicholas Nethercote [:njn] from comment #4)
> > The file is not executed as JS, it's just simply parsed as text
> 
> Ah.  Maybe changing the suffix to .txt would help avoid confusion?

At the expense of an awful lot of bustage. Given the few cases that I've heard of this causing problems I don't think it is worth it.
(Assignee)

Comment 6

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/0eb8564567df
https://hg.mozilla.org/mozilla-central/rev/0eb8564567df
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
Blocks: 787873

Comment 8

5 years ago
(In reply to Nicholas Nethercote from comment #2)
> Is this not a vanilla JS file?

It used to be before bug 98533 back in 2003...
You need to log in before you can comment on or make changes to this bug.